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. AirportTransferBookingView 
    2. BookingView 
    3. BookingStatusHistoryView 
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 AirportTransferBookingView must contain the following fields: 
    - name: AirportTransferProduct   type: AirportTransferProduct 
    - name: Booking   type: Booking 
    - name: Currency   type: Currency 
    - name: DropoffAddress   type: STRING 
    - name: Passengers   type: INT 
    - name: PickupAddress   type: STRING 
    - name: PickupDateTime   type: DATE 
    - name: TotalAmount   type: STRING 
The data source for the [Currency] select control should be loaded from the relative URL: 
    "/CurrencyService/currency"   (HTTP-GET) 
The data source for the [Booking] select control should be loaded from the relative URL: 
    "/BookingService/booking"   (HTTP-GET) 
The data source for the [AirportTransferProduct] select control should be loaded from the relative URL: 
    "/AirportService/airporttransferproduct"   (HTTP-GET) 
An existing AirportTransferBooking entity should be loaded from the relative URL: 
    "/BookingService/airporttransferbooking/{id}"   (HTTP-GET) 
If a new AirportTransferBooking entity has been created, the new entity should be posted to the relative URL: 
    "/BookingService/airporttransferbooking"   (HTTP-POST) 
If an existing AirportTransferBooking entity has been updated, the modified entity should be sent to the relative URL: 
    "/BookingService/airporttransferbooking/{id}"   (HTTP-PUT) 
If an existing AirportTransferBooking entity has to be deleted, the following relative URL should be called: 
    "/BookingService/airporttransferbooking/{id}"   (HTTP-DELETE)

2. The BookingView must contain the following fields: 
    - name: Channel   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: Currency   type: Currency 
    - name: DisplayAmount   type: STRING 
    - name: Status   type: STRING 
    - name: TotalAmount   type: STRING 
    - name: UpdatedAt   type: DATE 
    - name: UserAccount   type: UserAccount 
The data source for the [Currency] select control should be loaded from the relative URL: 
    "/CurrencyService/currency"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (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 StayBooking columns: 
    - column: Booking 
    - column: CheckOutDate 
    - column: RoomType 
    - column: Adults 
    - column: Children 
    - column: SpecialRequests 
    - column: NumberOfRooms 
    - column: RoomRatePlan 
    - column: CheckInDate 
    - column: BaseAmount 
    - column: Currency 
    - column: CancellationPolicySnapshot 
    - column: TaxesAmount 
    - column: Property 
    - column: FeesAmount 
The table should have the title "StayBookings" und the data must be loaded from the server with the following relative URL: 
    "/StayBookingService/staybooking/booking/{id}" 
Add a HTML table to the view with the following CarRentalBooking columns: 
    - column: TotalAmount 
    - column: CarRentalProduct 
    - column: DropoffLocation 
    - column: DropoffDateTime 
    - column: Booking 
    - column: PickupLocation 
    - column: Currency 
    - column: PickupDateTime 
The table should have the title "CarRentalBookings" und the data must be loaded from the server with the following relative URL: 
    "/CarRentalLocationService/carrentalbooking/booking/{id}" 
Add a HTML table to the view with the following FlightBooking columns: 
    - column: Booking 
    - column: Currency 
    - column: TotalAmount 
    - column: CabinClass 
    - column: PnrCode 
The table should have the title "FlightBookings" und the data must be loaded from the server with the following relative URL: 
    "/CurrencyService/flightbooking/booking/{id}" 
Add a HTML table to the view with the following Payment columns: 
    - column: Currency 
    - column: Booking 
    - column: Status 
    - column: ProviderReference 
    - column: Amount 
    - column: ProcessedAt 
    - column: CreatedAt 
    - column: PaymentMethod 
The table should have the title "Payments" und the data must be loaded from the server with the following relative URL: 
    "/CurrencyService/payment/booking/{id}" 
Add a HTML table to the view with the following AirportTransferBooking columns: 
    - column: PickupAddress 
    - column: Booking 
    - column: PickupDateTime 
    - column: Passengers 
    - column: DropoffAddress 
    - column: AirportTransferProduct 
    - column: TotalAmount 
    - column: Currency 
The table should have the title "AirportTransferBookings" und the data must be loaded from the server with the following relative URL: 
    "/BookingService/airporttransferbooking/booking/{id}" 
Add a HTML table to the view with the following Review columns: 
    - column: Attraction 
    - column: Text 
    - column: UserAccount 
    - column: Property 
    - column: Booking 
    - column: Language 
    - column: OverallScore 
    - column: AirportTransferProduct 
    - column: CarRentalProduct 
    - column: IsPublic 
    - column: Title 
    - column: CreatedAt 
The table should have the title "Reviews" und the data must be loaded from the server with the following relative URL: 
    "/LanguageService/review/booking/{id}" 
Add a HTML table to the view with the following AttractionBooking columns: 
    - column: TotalAmount 
    - column: Children 
    - column: Currency 
    - column: AttractionSchedule 
    - column: Booking 
    - column: Adults 
The table should have the title "AttractionBookings" und the data must be loaded from the server with the following relative URL: 
    "/AttractionBookingService/attractionbooking/booking/{id}" 
Add a HTML table to the view with the following BookingStatusHistory columns: 
    - column: Notes 
    - column: Status 
    - column: Booking 
    - column: ChangedBySystem 
    - column: ChangedAt 
The table should have the title "BookingStatusHistorys" und the data must be loaded from the server with the following relative URL: 
    "/BookingService/bookingstatushistory/booking/{id}"

3. The BookingStatusHistoryView must contain the following fields: 
    - name: Booking   type: Booking 
    - name: ChangedAt   type: DATE 
    - name: ChangedBySystem   type: BOOL 
    - name: Notes   type: STRING 
    - name: Status   type: STRING 
The data source for the [Booking] select control should be loaded from the relative URL: 
    "/BookingService/booking"   (HTTP-GET) 
An existing BookingStatusHistory entity should be loaded from the relative URL: 
    "/BookingService/bookingstatushistory/{id}"   (HTTP-GET) 
If a new BookingStatusHistory entity has been created, the new entity should be posted to the relative URL: 
    "/BookingService/bookingstatushistory"   (HTTP-POST) 
If an existing BookingStatusHistory entity has been updated, the modified entity should be sent to the relative URL: 
    "/BookingService/bookingstatushistory/{id}"   (HTTP-PUT) 
If an existing BookingStatusHistory entity has to be deleted, the following relative URL should be called: 
    "/BookingService/bookingstatushistory/{id}"   (HTTP-DELETE)