Prompt for the UserAccountApp

Please create a React-JS application for the UserAccountModule. The application  has to offer the following views for the user interface: 
    1. MapViewSessionView 
    2. MapViewWeatherLayerView 
    3. UserAccountView 
    4. UserSettingView 
    5. UserSubscriptionView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 5 views are defined below.

1. The MapViewSessionView must contain the following fields: 
    - name: CenterLatitude   type: DOUBLE 
    - name: CenterLongitude   type: DOUBLE 
    - name: ClientDevice   type: STRING 
    - name: ClientIp   type: STRING 
    - name: EndedAtUtc   type: DATE 
    - name: StartedAtUtc   type: DATE 
    - name: UserAccount   type: UserAccount 
    - name: ZoomLevel   type: INT 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing MapViewSession entity should be loaded from the relative URL: 
    "/UserAccountService/mapviewsession/{id}"   (HTTP-GET) 
If a new MapViewSession entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/mapviewsession"   (HTTP-POST) 
If an existing MapViewSession entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/mapviewsession/{id}"   (HTTP-PUT) 
If an existing MapViewSession entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/mapviewsession/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following MapViewWeatherLayer columns: 
    - column: MapViewSession 
    - column: WeatherLayer 
    - column: Visible 
The table should have the title "MapViewWeatherLayers" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/mapviewweatherlayer/mapviewsession/{id}" 
Add a HTML table to the view with the following MapViewFilterPreset columns: 
    - column: MapViewSession 
    - column: FilterPreset 
The table should have the title "MapViewFilterPresets" und the data must be loaded from the server with the following relative URL: 
    "/WeatherLayerService/mapviewfilterpreset/mapviewsession/{id}"

2. The MapViewWeatherLayerView must contain the following fields: 
    - name: MapViewSession   type: MapViewSession 
    - name: Visible   type: BOOL 
    - name: WeatherLayer   type: WeatherLayer 
The data source for the [WeatherLayer] select control should be loaded from the relative URL: 
    "/WeatherLayerService/weatherlayer"   (HTTP-GET) 
The data source for the [MapViewSession] select control should be loaded from the relative URL: 
    "/UserAccountService/mapviewsession"   (HTTP-GET) 
An existing MapViewWeatherLayer entity should be loaded from the relative URL: 
    "/UserAccountService/mapviewweatherlayer/{id}"   (HTTP-GET) 
If a new MapViewWeatherLayer entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/mapviewweatherlayer"   (HTTP-POST) 
If an existing MapViewWeatherLayer entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/mapviewweatherlayer/{id}"   (HTTP-PUT) 
If an existing MapViewWeatherLayer entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/mapviewweatherlayer/{id}"   (HTTP-DELETE)

3. The UserAccountView must contain the following fields: 
    - name: Country   type: STRING 
    - name: CreatedAtUtc   type: DATE 
    - name: DisplayName   type: STRING 
    - name: Email   type: STRING 
    - name: IsAdmin   type: BOOL 
    - name: LastLoginAtUtc   type: DATE 
    - name: PasswordHash   type: STRING 
    - name: SubscriptionPlan   type: INT 
An existing UserAccount entity should be loaded from the relative URL: 
    "/UserAccountService/useraccount/{id}"   (HTTP-GET) 
If a new UserAccount entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-POST) 
If an existing UserAccount entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/useraccount/{id}"   (HTTP-PUT) 
If an existing UserAccount entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/useraccount/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Alert columns: 
    - column: Type 
    - column: CreatedAtUtc 
    - column: Active 
    - column: Flight 
    - column: TriggerConditionJson 
    - column: UserAccount 
The table should have the title "Alerts" und the data must be loaded from the server with the following relative URL: 
    "/FlightService/alert/useraccount/{id}" 
Add a HTML table to the view with the following MapViewSession columns: 
    - column: CenterLongitude 
    - column: ZoomLevel 
    - column: ClientIp 
    - column: ClientDevice 
    - column: UserAccount 
    - column: StartedAtUtc 
    - column: EndedAtUtc 
    - column: CenterLatitude 
The table should have the title "MapViewSessions" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/mapviewsession/useraccount/{id}" 
Add a HTML table to the view with the following AdImpression columns: 
    - column: RevenueShare 
    - column: Advertisement 
    - column: Clicked 
    - column: UserAccount 
    - column: ShownAtUtc 
The table should have the title "AdImpressions" und the data must be loaded from the server with the following relative URL: 
    "/AdvertisementService/adimpression/useraccount/{id}" 
Add a HTML table to the view with the following Receiver columns: 
    - column: SerialNumber 
    - column: SourceType 
    - column: InstallDate 
    - column: OwnerUser 
    - column: Latitude 
    - column: Active 
    - column: Longitude 
    - column: AltitudeFt 
    - column: Name 
The table should have the title "Receivers" und the data must be loaded from the server with the following relative URL: 
    "/ReceiverService/receiver/owneruser/{id}" 
Add a HTML table to the view with the following UserSubscription columns: 
    - column: EndDateUtc 
    - column: SubscriptionPlan 
    - column: AutoRenew 
    - column: Status 
    - column: UserAccount 
    - column: StartDateUtc 
The table should have the title "UserSubscriptions" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/usersubscription/useraccount/{id}" 
Add a HTML table to the view with the following AdBlockDetectionEvent columns: 
    - column: MessageShown 
    - column: UserAccount 
    - column: DetectedAtUtc 
    - column: ActionTaken 
The table should have the title "AdBlockDetectionEvents" und the data must be loaded from the server with the following relative URL: 
    "/AircraftService/adblockdetectionevent/useraccount/{id}" 
Add a HTML table to the view with the following FilterPreset columns: 
    - column: Shared 
    - column: CriteriaJson 
    - column: Name 
    - column: UserAccount 
    - column: CreatedAtUtc 
The table should have the title "FilterPresets" und the data must be loaded from the server with the following relative URL: 
    "/WeatherLayerService/filterpreset/useraccount/{id}" 
Add a HTML table to the view with the following UserSetting columns: 
    - column: UserKey 
    - column: UserValue 
    - column: UserAccount 
The table should have the title "UserSettings" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/usersetting/useraccount/{id}"

4. The UserSettingView must contain the following fields: 
    - name: UserAccount   type: UserAccount 
    - name: UserKey   type: STRING 
    - name: UserValue   type: STRING 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing UserSetting entity should be loaded from the relative URL: 
    "/UserAccountService/usersetting/{id}"   (HTTP-GET) 
If a new UserSetting entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/usersetting"   (HTTP-POST) 
If an existing UserSetting entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/usersetting/{id}"   (HTTP-PUT) 
If an existing UserSetting entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/usersetting/{id}"   (HTTP-DELETE)

5. The UserSubscriptionView must contain the following fields: 
    - name: AutoRenew   type: BOOL 
    - name: EndDateUtc   type: DATE 
    - name: StartDateUtc   type: DATE 
    - name: Status   type: STRING 
    - name: SubscriptionPlan   type: SubscriptionPlan 
    - name: UserAccount   type: UserAccount 
The data source for the [SubscriptionPlan] select control should be loaded from the relative URL: 
    "/AdvertisementService/subscriptionplan"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing UserSubscription entity should be loaded from the relative URL: 
    "/UserAccountService/usersubscription/{id}"   (HTTP-GET) 
If a new UserSubscription entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/usersubscription"   (HTTP-POST) 
If an existing UserSubscription entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/usersubscription/{id}"   (HTTP-PUT) 
If an existing UserSubscription entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/usersubscription/{id}"   (HTTP-DELETE)