Prompt for the BookingApp

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

1. The BookingView must contain the following fields: 
    - name: BookingStatus   type: STRING 
    - name: CancellationPolicy   type: STRING 
    - name: CancelledAt   type: DATE 
    - name: CheckInDate   type: DATE 
    - name: CheckOutDate   type: DATE 
    - name: CleaningFee   type: DOUBLE 
    - name: ConfirmedAt   type: DATE 
    - name: CreatedAt   type: DATE 
    - name: Currency   type: STRING 
    - name: GuestProfile   type: GuestProfile 
    - name: Listing   type: Listing 
    - name: NumberOfGuests   type: INT 
    - name: ServiceFeeGuest   type: DOUBLE 
    - name: ServiceFeeHost   type: DOUBLE 
    - name: TotalPrice   type: DOUBLE 
The data source for the [GuestProfile] select control should be loaded from the relative URL: 
    "/BookingService/guestprofile"   (HTTP-GET) 
The data source for the [Listing] select control should be loaded from the relative URL: 
    "/ListingService/listing"   (HTTP-GET) 
An existing Booking entity should be loaded from the relative URL: 
    "/BookingService/booking/{id}"   (HTTP-GET) 
If a new Booking entity has been created, the new entity should be posted to the relative URL: 
    "/BookingService/booking"   (HTTP-POST) 
If an existing Booking entity has been updated, the modified entity should be sent to the relative URL: 
    "/BookingService/booking/{id}"   (HTTP-PUT) 
If an existing Booking entity has to be deleted, the following relative URL should be called: 
    "/BookingService/booking/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Review columns: 
    - column: RatingLocation 
    - column: RatingValue 
    - column: RatingCommunication 
    - column: RatingOverall 
    - column: Reviewee 
    - column: Reviewer 
    - column: ReviewType 
    - column: CreatedAt 
    - column: Booking 
    - column: Comment 
    - column: RatingCleanliness 
The table should have the title "Reviews" und the data must be loaded from the server with the following relative URL: 
    "/MarketService/review/booking/{id}" 
Add a HTML table to the view with the following Payout columns: 
    - column: Booking 
    - column: PayoutDate 
    - column: Amount 
    - column: PayoutMethod 
    - column: HostProfile 
    - column: PayoutStatus 
    - column: Currency 
The table should have the title "Payouts" und the data must be loaded from the server with the following relative URL: 
    "/HostProfileService/payout/booking/{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/booking/{id}"

2. 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: 
    "/BookingService/guestprofile/{id}"   (HTTP-GET) 
If a new GuestProfile entity has been created, the new entity should be posted to the relative URL: 
    "/BookingService/guestprofile"   (HTTP-POST) 
If an existing GuestProfile entity has been updated, the modified entity should be sent to the relative URL: 
    "/BookingService/guestprofile/{id}"   (HTTP-PUT) 
If an existing GuestProfile entity has to be deleted, the following relative URL should be called: 
    "/BookingService/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: 
    "/BookingService/booking/guestprofile/{id}"

3. 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: 
    "/BookingService/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: 
    "/BookingService/payment/{id}"   (HTTP-GET) 
If a new Payment entity has been created, the new entity should be posted to the relative URL: 
    "/BookingService/payment"   (HTTP-POST) 
If an existing Payment entity has been updated, the modified entity should be sent to the relative URL: 
    "/BookingService/payment/{id}"   (HTTP-PUT) 
If an existing Payment entity has to be deleted, the following relative URL should be called: 
    "/BookingService/payment/{id}"   (HTTP-DELETE)

4. The TaxCaseView must contain the following fields: 
    - name: AmountAssessed   type: DOUBLE 
    - name: Company   type: Company 
    - name: Currency   type: STRING 
    - name: Description   type: STRING 
    - name: EndDate   type: DATE 
    - name: Jurisdiction   type: Jurisdiction 
    - name: StartDate   type: DATE 
    - name: Status   type: STRING 
The data source for the [Jurisdiction] select control should be loaded from the relative URL: 
    "/JurisdictionService/jurisdiction"   (HTTP-GET) 
The data source for the [Company] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
An existing TaxCase entity should be loaded from the relative URL: 
    "/BookingService/taxcase/{id}"   (HTTP-GET) 
If a new TaxCase entity has been created, the new entity should be posted to the relative URL: 
    "/BookingService/taxcase"   (HTTP-POST) 
If an existing TaxCase entity has been updated, the modified entity should be sent to the relative URL: 
    "/BookingService/taxcase/{id}"   (HTTP-PUT) 
If an existing TaxCase entity has to be deleted, the following relative URL should be called: 
    "/BookingService/taxcase/{id}"   (HTTP-DELETE)