Prompt for the UserProfileApp

Please create a React-JS application for the UserProfileModule. The application  has to offer the following views for the user interface: 
    1. RecommendationEventView 
    2. UserAccountView 
    3. UserProfileView 
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 RecommendationEventView must contain the following fields: 
    - name: ContentTitle   type: ContentTitle 
    - name: EventDate   type: DATE 
    - name: EventType   type: STRING 
    - name: RatingValue   type: STRING 
    - name: RecommendationAlgorithm   type: RecommendationAlgorithm 
    - name: UserProfile   type: UserProfile 
The data source for the [UserProfile] select control should be loaded from the relative URL: 
    "/UserProfileService/userprofile"   (HTTP-GET) 
The data source for the [ContentTitle] select control should be loaded from the relative URL: 
    "/ContentTitleService/contenttitle"   (HTTP-GET) 
The data source for the [RecommendationAlgorithm] select control should be loaded from the relative URL: 
    "/RecommendationAlgorithmService/recommendationalgorithm"   (HTTP-GET) 
An existing RecommendationEvent entity should be loaded from the relative URL: 
    "/UserProfileService/recommendationevent/{id}"   (HTTP-GET) 
If a new RecommendationEvent entity has been created, the new entity should be posted to the relative URL: 
    "/UserProfileService/recommendationevent"   (HTTP-POST) 
If an existing RecommendationEvent entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserProfileService/recommendationevent/{id}"   (HTTP-PUT) 
If an existing RecommendationEvent entity has to be deleted, the following relative URL should be called: 
    "/UserProfileService/recommendationevent/{id}"   (HTTP-DELETE)

2. The UserAccountView must contain the following fields: 
    - name: Country   type: Country 
    - name: CreatedAt   type: DATE 
    - name: Email   type: STRING 
    - name: Status   type: STRING 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/CountryService/country"   (HTTP-GET) 
An existing UserAccount entity should be loaded from the relative URL: 
    "/UserProfileService/useraccount/{id}"   (HTTP-GET) 
If a new UserAccount entity has been created, the new entity should be posted to the relative URL: 
    "/UserProfileService/useraccount"   (HTTP-POST) 
If an existing UserAccount entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserProfileService/useraccount/{id}"   (HTTP-PUT) 
If an existing UserAccount entity has to be deleted, the following relative URL should be called: 
    "/UserProfileService/useraccount/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Membership columns: 
    - column: StartDate 
    - column: SubscriptionPlan 
    - column: EndDate 
    - column: UserAccount 
    - column: Status 
The table should have the title "Memberships" und the data must be loaded from the server with the following relative URL: 
    "/SubscriptionPlanService/membership/useraccount/{id}" 
Add a HTML table to the view with the following UserProfile columns: 
    - column: UserAccount 
    - column: MaturityLevel 
    - column: Name 
    - column: CreatedAt 
The table should have the title "UserProfiles" und the data must be loaded from the server with the following relative URL: 
    "/UserProfileService/userprofile/useraccount/{id}"

3. The UserProfileView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: MaturityLevel   type: STRING 
    - name: Name   type: STRING 
    - name: UserAccount   type: UserAccount 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserProfileService/useraccount"   (HTTP-GET) 
An existing UserProfile entity should be loaded from the relative URL: 
    "/UserProfileService/userprofile/{id}"   (HTTP-GET) 
If a new UserProfile entity has been created, the new entity should be posted to the relative URL: 
    "/UserProfileService/userprofile"   (HTTP-POST) 
If an existing UserProfile entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserProfileService/userprofile/{id}"   (HTTP-PUT) 
If an existing UserProfile entity has to be deleted, the following relative URL should be called: 
    "/UserProfileService/userprofile/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following RecommendationEvent columns: 
    - column: RatingValue 
    - column: EventType 
    - column: EventDate 
    - column: UserProfile 
    - column: ContentTitle 
    - column: RecommendationAlgorithm 
The table should have the title "RecommendationEvents" und the data must be loaded from the server with the following relative URL: 
    "/UserProfileService/recommendationevent/userprofile/{id}" 
Add a HTML table to the view with the following PlaybackSession columns: 
    - column: EndedAt 
    - column: DurationSeconds 
    - column: UserProfile 
    - column: ContentTitle 
    - column: StartedAt 
    - column: Device 
    - column: WasCompleted 
The table should have the title "PlaybackSessions" und the data must be loaded from the server with the following relative URL: 
    "/DeviceService/playbacksession/userprofile/{id}"