Prompt for the PlatformUserApp

Please create a React-JS application for the PlatformUserModule. The application  has to offer the following views for the user interface: 
    1. GuestProfileView 
    2. PaymentView 
    3. PlatformUserView 
    4. UserDataConsentView 
    5. UserIdentityDocumentView 
    6. UserRoleView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 6 views are defined below.

1. The GuestProfileView must contain the following fields: 
    - name: About   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: OverallRating   type: DOUBLE 
    - name: PlatformUser   type: PlatformUser 
    - name: TripsCount   type: INT 
The data source for the [PlatformUser] select control should be loaded from the relative URL: 
    "/PlatformUserService/platformuser"   (HTTP-GET) 
An existing GuestProfile entity should be loaded from the relative URL: 
    "/PlatformUserService/guestprofile/{id}"   (HTTP-GET) 
If a new GuestProfile entity has been created, the new entity should be posted to the relative URL: 
    "/PlatformUserService/guestprofile"   (HTTP-POST) 
If an existing GuestProfile entity has been updated, the modified entity should be sent to the relative URL: 
    "/PlatformUserService/guestprofile/{id}"   (HTTP-PUT) 
If an existing GuestProfile entity has to be deleted, the following relative URL should be called: 
    "/PlatformUserService/guestprofile/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Booking columns: 
    - column: CleaningFee 
    - column: Listing 
    - column: CheckInDate 
    - column: BookingStatus 
    - column: GuestProfile 
    - column: CreatedAt 
    - column: CancellationPolicy 
    - column: CheckOutDate 
    - column: ServiceFeeGuest 
    - column: TotalPrice 
    - column: ServiceFeeHost 
    - column: CancelledAt 
    - column: Currency 
    - column: ConfirmedAt 
    - column: NumberOfGuests 
The table should have the title "Bookings" und the data must be loaded from the server with the following relative URL: 
    "/ListingService/booking/guestprofile/{id}"

2. The PaymentView must contain the following fields: 
    - name: Amount   type: DOUBLE 
    - name: Booking   type: Booking 
    - name: Currency   type: STRING 
    - name: ExternalTransactionReference   type: STRING 
    - name: PaidAt   type: DATE 
    - name: PaymentMethod   type: STRING 
    - name: PaymentStatus   type: STRING 
    - name: PlatformUser   type: PlatformUser 
The data source for the [Booking] select control should be loaded from the relative URL: 
    "/ListingService/booking"   (HTTP-GET) 
The data source for the [PlatformUser] select control should be loaded from the relative URL: 
    "/PlatformUserService/platformuser"   (HTTP-GET) 
An existing Payment entity should be loaded from the relative URL: 
    "/PlatformUserService/payment/{id}"   (HTTP-GET) 
If a new Payment entity has been created, the new entity should be posted to the relative URL: 
    "/PlatformUserService/payment"   (HTTP-POST) 
If an existing Payment entity has been updated, the modified entity should be sent to the relative URL: 
    "/PlatformUserService/payment/{id}"   (HTTP-PUT) 
If an existing Payment entity has to be deleted, the following relative URL should be called: 
    "/PlatformUserService/payment/{id}"   (HTTP-DELETE)

3. The PlatformUserView must contain the following fields: 
    - name: City   type: City 
    - name: Country   type: Country 
    - name: CreatedAt   type: DATE 
    - name: DateOfBirth   type: DATE 
    - name: Email   type: STRING 
    - name: FacebookProfileUrl   type: STRING 
    - name: FullName   type: STRING 
    - name: GoogleProfileUrl   type: STRING 
    - name: LinkedinProfileUrl   type: STRING 
    - name: PhoneNumber   type: STRING 
    - name: ProfilePhotoUrl   type: STRING 
    - name: UpdatedAt   type: DATE 
    - name: VerificationLevel   type: STRING 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/CountryService/country"   (HTTP-GET) 
The data source for the [City] select control should be loaded from the relative URL: 
    "/ListingService/city"   (HTTP-GET) 
An existing PlatformUser entity should be loaded from the relative URL: 
    "/PlatformUserService/platformuser/{id}"   (HTTP-GET) 
If a new PlatformUser entity has been created, the new entity should be posted to the relative URL: 
    "/PlatformUserService/platformuser"   (HTTP-POST) 
If an existing PlatformUser entity has been updated, the modified entity should be sent to the relative URL: 
    "/PlatformUserService/platformuser/{id}"   (HTTP-PUT) 
If an existing PlatformUser entity has to be deleted, the following relative URL should be called: 
    "/PlatformUserService/platformuser/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following HostProfile columns: 
    - column: IsSuperhost 
    - column: ResponseRate 
    - column: SuperhostSince 
    - column: About 
    - column: CreatedAt 
    - column: PlatformUser 
    - column: ResponseTime 
    - column: OverallRating 
The table should have the title "HostProfiles" und the data must be loaded from the server with the following relative URL: 
    "/HostProfileService/hostprofile/platformuser/{id}" 
Add a HTML table to the view with the following UserDataConsent columns: 
    - column: ConsentType 
    - column: RevokedAt 
    - column: PlatformUser 
    - column: GrantedAt 
    - column: Description 
The table should have the title "UserDataConsents" und the data must be loaded from the server with the following relative URL: 
    "/PlatformUserService/userdataconsent/platformuser/{id}" 
Add a HTML table to the view with the following UserIdentityDocument columns: 
    - column: ExpiryDate 
    - column: VerificationStatus 
    - column: IssuingCountry 
    - column: DocumentNumber 
    - column: PlatformUser 
    - column: DocumentType 
    - column: CreatedAt 
The table should have the title "UserIdentityDocuments" und the data must be loaded from the server with the following relative URL: 
    "/PlatformUserService/useridentitydocument/platformuser/{id}" 
Add a HTML table to the view with the following FraudCase columns: 
    - column: PlatformUserReporter 
    - column: ResolvedAt 
    - column: Status 
    - column: Listing 
    - column: CaseType 
    - column: Description 
    - column: ReportedAt 
The table should have the title "FraudCases" und the data must be loaded from the server with the following relative URL: 
    "/ListingService/fraudcase/platformuserreporter/{id}" 
Add a HTML table to the view with the following UserRole columns: 
    - column: RoleType 
    - column: CreatedAt 
    - column: PlatformUser 
The table should have the title "UserRoles" und the data must be loaded from the server with the following relative URL: 
    "/PlatformUserService/userrole/platformuser/{id}" 
Add a HTML table to the view with the following GuestProfile columns: 
    - column: CreatedAt 
    - column: About 
    - column: TripsCount 
    - column: PlatformUser 
    - column: OverallRating 
The table should have the title "GuestProfiles" und the data must be loaded from the server with the following relative URL: 
    "/PlatformUserService/guestprofile/platformuser/{id}" 
Add a HTML table to the view with the following Payment columns: 
    - column: Booking 
    - column: PaymentStatus 
    - column: PaidAt 
    - column: Currency 
    - column: ExternalTransactionReference 
    - column: PlatformUser 
    - column: Amount 
    - column: PaymentMethod 
The table should have the title "Payments" und the data must be loaded from the server with the following relative URL: 
    "/PlatformUserService/payment/platformuser/{id}"

4. The UserDataConsentView must contain the following fields: 
    - name: ConsentType   type: STRING 
    - name: Description   type: STRING 
    - name: GrantedAt   type: DATE 
    - name: PlatformUser   type: PlatformUser 
    - name: RevokedAt   type: DATE 
The data source for the [PlatformUser] select control should be loaded from the relative URL: 
    "/PlatformUserService/platformuser"   (HTTP-GET) 
An existing UserDataConsent entity should be loaded from the relative URL: 
    "/PlatformUserService/userdataconsent/{id}"   (HTTP-GET) 
If a new UserDataConsent entity has been created, the new entity should be posted to the relative URL: 
    "/PlatformUserService/userdataconsent"   (HTTP-POST) 
If an existing UserDataConsent entity has been updated, the modified entity should be sent to the relative URL: 
    "/PlatformUserService/userdataconsent/{id}"   (HTTP-PUT) 
If an existing UserDataConsent entity has to be deleted, the following relative URL should be called: 
    "/PlatformUserService/userdataconsent/{id}"   (HTTP-DELETE)

5. The UserIdentityDocumentView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: DocumentNumber   type: STRING 
    - name: DocumentType   type: STRING 
    - name: ExpiryDate   type: DATE 
    - name: IssuingCountry   type: LONG 
    - name: PlatformUser   type: PlatformUser 
    - name: VerificationStatus   type: STRING 
The data source for the [PlatformUser] select control should be loaded from the relative URL: 
    "/PlatformUserService/platformuser"   (HTTP-GET) 
An existing UserIdentityDocument entity should be loaded from the relative URL: 
    "/PlatformUserService/useridentitydocument/{id}"   (HTTP-GET) 
If a new UserIdentityDocument entity has been created, the new entity should be posted to the relative URL: 
    "/PlatformUserService/useridentitydocument"   (HTTP-POST) 
If an existing UserIdentityDocument entity has been updated, the modified entity should be sent to the relative URL: 
    "/PlatformUserService/useridentitydocument/{id}"   (HTTP-PUT) 
If an existing UserIdentityDocument entity has to be deleted, the following relative URL should be called: 
    "/PlatformUserService/useridentitydocument/{id}"   (HTTP-DELETE)

6. The UserRoleView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: PlatformUser   type: PlatformUser 
    - name: RoleType   type: STRING 
The data source for the [PlatformUser] select control should be loaded from the relative URL: 
    "/PlatformUserService/platformuser"   (HTTP-GET) 
An existing UserRole entity should be loaded from the relative URL: 
    "/PlatformUserService/userrole/{id}"   (HTTP-GET) 
If a new UserRole entity has been created, the new entity should be posted to the relative URL: 
    "/PlatformUserService/userrole"   (HTTP-POST) 
If an existing UserRole entity has been updated, the modified entity should be sent to the relative URL: 
    "/PlatformUserService/userrole/{id}"   (HTTP-PUT) 
If an existing UserRole entity has to be deleted, the following relative URL should be called: 
    "/PlatformUserService/userrole/{id}"   (HTTP-DELETE)