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. FraudCaseView 
    2. PlatformUserView 
    3. 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 3 views are defined below.

1. The FraudCaseView must contain the following fields: 
    - name: CaseType   type: STRING 
    - name: Description   type: STRING 
    - name: Listing   type: Listing 
    - name: PlatformUserReporter   type: PlatformUser 
    - name: ReportedAt   type: DATE 
    - name: ResolvedAt   type: DATE 
    - name: Status   type: STRING 
The data source for the [Listing] select control should be loaded from the relative URL: 
    "/ListingService/listing"   (HTTP-GET) 
The data source for the [PlatformUserReporter] select control should be loaded from the relative URL: 
    "/PlatformUserService/platformuser"   (HTTP-GET) 
An existing FraudCase entity should be loaded from the relative URL: 
    "/PlatformUserService/fraudcase/{id}"   (HTTP-GET) 
If a new FraudCase entity has been created, the new entity should be posted to the relative URL: 
    "/PlatformUserService/fraudcase"   (HTTP-POST) 
If an existing FraudCase entity has been updated, the modified entity should be sent to the relative URL: 
    "/PlatformUserService/fraudcase/{id}"   (HTTP-PUT) 
If an existing FraudCase entity has to be deleted, the following relative URL should be called: 
    "/PlatformUserService/fraudcase/{id}"   (HTTP-DELETE)

2. 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: 
    "/AmenityService/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: 
    "/MessageThreadService/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: 
    "/PlatformUserService/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: 
    "/BookingService/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: 
    "/BookingService/payment/platformuser/{id}"

3. 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)