Prompt for the TrendLocationApp

Please create a React-JS application for the TrendLocationModule. The application  has to offer the following views for the user interface: 
    1. ApiAccessTokenView 
    2. TrendLocationView 
    3. TrendTopicView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 3 views are defined below.

1. The ApiAccessTokenView must contain the following fields: 
    - name: ApiApp   type: ApiApp 
    - name: CreatedAt   type: STRING 
    - name: ExpiresAt   type: STRING 
    - name: Scope   type: STRING 
    - name: Token   type: STRING 
    - name: User   type: UserAccount 
The data source for the [ApiApp] select control should be loaded from the relative URL: 
    "/UserAccountService/apiapp"   (HTTP-GET) 
The data source for the [User] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing ApiAccessToken entity should be loaded from the relative URL: 
    "/TrendLocationService/apiaccesstoken/{id}"   (HTTP-GET) 
If a new ApiAccessToken entity has been created, the new entity should be posted to the relative URL: 
    "/TrendLocationService/apiaccesstoken"   (HTTP-POST) 
If an existing ApiAccessToken entity has been updated, the modified entity should be sent to the relative URL: 
    "/TrendLocationService/apiaccesstoken/{id}"   (HTTP-PUT) 
If an existing ApiAccessToken entity has to be deleted, the following relative URL should be called: 
    "/TrendLocationService/apiaccesstoken/{id}"   (HTTP-DELETE)

2. The TrendLocationView must contain the following fields: 
    - name: Country   type: STRING 
    - name: CountryCode   type: STRING 
    - name: Name   type: STRING 
    - name: Woeid   type: LONG 
An existing TrendLocation entity should be loaded from the relative URL: 
    "/TrendLocationService/trendlocation/{id}"   (HTTP-GET) 
If a new TrendLocation entity has been created, the new entity should be posted to the relative URL: 
    "/TrendLocationService/trendlocation"   (HTTP-POST) 
If an existing TrendLocation entity has been updated, the modified entity should be sent to the relative URL: 
    "/TrendLocationService/trendlocation/{id}"   (HTTP-PUT) 
If an existing TrendLocation entity has to be deleted, the following relative URL should be called: 
    "/TrendLocationService/trendlocation/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following TrendTopic columns: 
    - column: TrendLocation 
    - column: Query 
    - column: AsOf 
    - column: Name 
    - column: Url 
    - column: PromotedContent 
The table should have the title "TrendTopics" und the data must be loaded from the server with the following relative URL: 
    "/TrendLocationService/trendtopic/trendlocation/{id}"

3. The TrendTopicView must contain the following fields: 
    - name: AsOf   type: STRING 
    - name: Name   type: STRING 
    - name: PromotedContent   type: STRING 
    - name: Query   type: STRING 
    - name: TrendLocation   type: TrendLocation 
    - name: Url   type: STRING 
The data source for the [TrendLocation] select control should be loaded from the relative URL: 
    "/TrendLocationService/trendlocation"   (HTTP-GET) 
An existing TrendTopic entity should be loaded from the relative URL: 
    "/TrendLocationService/trendtopic/{id}"   (HTTP-GET) 
If a new TrendTopic entity has been created, the new entity should be posted to the relative URL: 
    "/TrendLocationService/trendtopic"   (HTTP-POST) 
If an existing TrendTopic entity has been updated, the modified entity should be sent to the relative URL: 
    "/TrendLocationService/trendtopic/{id}"   (HTTP-PUT) 
If an existing TrendTopic entity has to be deleted, the following relative URL should be called: 
    "/TrendLocationService/trendtopic/{id}"   (HTTP-DELETE)