Prompt for the CustomerApp

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

1. The BookingView must contain the following fields: 
    - name: BookingCode   type: STRING 
    - name: BookingDateTime   type: DATE 
    - name: Currency   type: STRING 
    - name: Customer   type: Customer 
    - name: Flight   type: Flight 
    - name: Status   type: STRING 
    - name: TotalPrice   type: STRING 
The data source for the [Customer] select control should be loaded from the relative URL: 
    "/CustomerService/customer"   (HTTP-GET) 
The data source for the [Flight] select control should be loaded from the relative URL: 
    "/FlightService/flight"   (HTTP-GET) 
An existing Booking entity should be loaded from the relative URL: 
    "/CustomerService/booking/{id}"   (HTTP-GET) 
If a new Booking entity has been created, the new entity should be posted to the relative URL: 
    "/CustomerService/booking"   (HTTP-POST) 
If an existing Booking entity has been updated, the modified entity should be sent to the relative URL: 
    "/CustomerService/booking/{id}"   (HTTP-PUT) 
If an existing Booking entity has to be deleted, the following relative URL should be called: 
    "/CustomerService/booking/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following GiftRedemption columns: 
    - column: RedemptionDate 
    - column: Currency 
    - column: AmountApplied 
    - column: GiftVoucher 
    - column: Booking 
The table should have the title "GiftRedemptions" und the data must be loaded from the server with the following relative URL: 
    "/GiftVoucherService/giftredemption/booking/{id}" 
Add a HTML table to the view with the following BookingSeat columns: 
    - column: Currency 
    - column: FlightSeat 
    - column: Price 
    - column: Booking 
The table should have the title "BookingSeats" und the data must be loaded from the server with the following relative URL: 
    "/FlightService/bookingseat/booking/{id}" 
Add a HTML table to the view with the following Payment columns: 
    - column: Currency 
    - column: PaymentMethod 
    - column: TransactionReference 
    - column: Amount 
    - column: Booking 
    - column: PaymentDateTime 
    - column: Status 
The table should have the title "Payments" und the data must be loaded from the server with the following relative URL: 
    "/CustomerService/payment/booking/{id}"

2. The CustomerView must contain the following fields: 
    - name: AddressLine1   type: STRING 
    - name: AddressLine2   type: STRING 
    - name: City   type: STRING 
    - name: Country   type: Country 
    - name: Email   type: STRING 
    - name: FirstName   type: STRING 
    - name: LastName   type: STRING 
    - name: Phone   type: STRING 
    - name: PostalCode   type: STRING 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/CountryService/country"   (HTTP-GET) 
An existing Customer entity should be loaded from the relative URL: 
    "/CustomerService/customer/{id}"   (HTTP-GET) 
If a new Customer entity has been created, the new entity should be posted to the relative URL: 
    "/CustomerService/customer"   (HTTP-POST) 
If an existing Customer entity has been updated, the modified entity should be sent to the relative URL: 
    "/CustomerService/customer/{id}"   (HTTP-PUT) 
If an existing Customer entity has to be deleted, the following relative URL should be called: 
    "/CustomerService/customer/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Booking columns: 
    - column: Flight 
    - column: BookingCode 
    - column: Status 
    - column: BookingDateTime 
    - column: TotalPrice 
    - column: Currency 
    - column: Customer 
The table should have the title "Bookings" und the data must be loaded from the server with the following relative URL: 
    "/CustomerService/booking/customer/{id}" 
Add a HTML table to the view with the following CustomerOrder columns: 
    - column: OrderNumber 
    - column: Customer 
    - column: Status 
    - column: TotalAmount 
    - column: Currency 
    - column: OrderDateTime 
The table should have the title "CustomerOrders" und the data must be loaded from the server with the following relative URL: 
    "/CustomerService/customerorder/customer/{id}" 
Add a HTML table to the view with the following GiftVoucher columns: 
    - column: Currency 
    - column: IssueDate 
    - column: ExpiryDate 
    - column: ValueAmount 
    - column: Code 
    - column: PurchaserCustomer 
    - column: IsRedeemed 
The table should have the title "GiftVouchers" und the data must be loaded from the server with the following relative URL: 
    "/GiftVoucherService/giftvoucher/purchasercustomer/{id}" 
Add a HTML table to the view with the following Reservation columns: 
    - column: Restaurant 
    - column: Status 
    - column: ReservationDateTime 
    - column: PartySize 
    - column: Customer 
    - column: Notes 
The table should have the title "Reservations" und the data must be loaded from the server with the following relative URL: 
    "/CustomerService/reservation/customer/{id}"

3. The CustomerOrderView must contain the following fields: 
    - name: Currency   type: STRING 
    - name: Customer   type: Customer 
    - name: OrderDateTime   type: DATE 
    - name: OrderNumber   type: STRING 
    - name: Status   type: STRING 
    - name: TotalAmount   type: STRING 
The data source for the [Customer] select control should be loaded from the relative URL: 
    "/CustomerService/customer"   (HTTP-GET) 
An existing CustomerOrder entity should be loaded from the relative URL: 
    "/CustomerService/customerorder/{id}"   (HTTP-GET) 
If a new CustomerOrder entity has been created, the new entity should be posted to the relative URL: 
    "/CustomerService/customerorder"   (HTTP-POST) 
If an existing CustomerOrder entity has been updated, the modified entity should be sent to the relative URL: 
    "/CustomerService/customerorder/{id}"   (HTTP-PUT) 
If an existing CustomerOrder entity has to be deleted, the following relative URL should be called: 
    "/CustomerService/customerorder/{id}"   (HTTP-DELETE)

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

5. The ReservationView must contain the following fields: 
    - name: Customer   type: Customer 
    - name: Notes   type: STRING 
    - name: PartySize   type: INT 
    - name: ReservationDateTime   type: DATE 
    - name: Restaurant   type: Restaurant 
    - name: Status   type: STRING 
The data source for the [Restaurant] select control should be loaded from the relative URL: 
    "/RestaurantService/restaurant"   (HTTP-GET) 
The data source for the [Customer] select control should be loaded from the relative URL: 
    "/CustomerService/customer"   (HTTP-GET) 
An existing Reservation entity should be loaded from the relative URL: 
    "/CustomerService/reservation/{id}"   (HTTP-GET) 
If a new Reservation entity has been created, the new entity should be posted to the relative URL: 
    "/CustomerService/reservation"   (HTTP-POST) 
If an existing Reservation entity has been updated, the modified entity should be sent to the relative URL: 
    "/CustomerService/reservation/{id}"   (HTTP-PUT) 
If an existing Reservation entity has to be deleted, the following relative URL should be called: 
    "/CustomerService/reservation/{id}"   (HTTP-DELETE)