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. ConferenceBookingView 
    3. CustomerView 
    4. CustomerAddressView 
    5. PaymentView 
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: BookingDate   type: DATE 
    - name: BookingNumber   type: STRING 
    - name: Currency   type: STRING 
    - name: Customer   type: Customer 
    - 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 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 BookingItem columns: 
    - column: Quantity 
    - column: Event 
    - column: Seat 
    - column: UnitPrice 
    - column: EventTicketType 
    - column: Booking 
    - column: TotalPrice 
The table should have the title "BookingItems" und the data must be loaded from the server with the following relative URL: 
    "/EventService/bookingitem/booking/{id}" 
Add a HTML table to the view with the following Payment columns: 
    - column: Currency 
    - column: PaymentStatus 
    - column: TransactionReference 
    - column: PaymentMethod 
    - column: Booking 
    - column: CreatedAt 
    - column: Amount 
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 ConferenceBookingView must contain the following fields: 
    - name: AttendeeCount   type: LONG 
    - name: ConferenceRoom   type: ConferenceRoom 
    - name: CreatedAt   type: DATE 
    - name: Customer   type: Customer 
    - name: Description   type: STRING 
    - name: EndDateTime   type: DATE 
    - name: StartDateTime   type: DATE 
    - name: Status   type: STRING 
    - name: Title   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 [ConferenceRoom] select control should be loaded from the relative URL: 
    "/ConferenceRoomService/conferenceroom"   (HTTP-GET) 
An existing ConferenceBooking entity should be loaded from the relative URL: 
    "/CustomerService/conferencebooking/{id}"   (HTTP-GET) 
If a new ConferenceBooking entity has been created, the new entity should be posted to the relative URL: 
    "/CustomerService/conferencebooking"   (HTTP-POST) 
If an existing ConferenceBooking entity has been updated, the modified entity should be sent to the relative URL: 
    "/CustomerService/conferencebooking/{id}"   (HTTP-PUT) 
If an existing ConferenceBooking entity has to be deleted, the following relative URL should be called: 
    "/CustomerService/conferencebooking/{id}"   (HTTP-DELETE)

3. The CustomerView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: Email   type: STRING 
    - name: FirstName   type: STRING 
    - name: LastName   type: STRING 
    - name: PhoneNumber   type: STRING 
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: BookingNumber 
    - column: Currency 
    - column: BookingDate 
    - column: Status 
    - column: Customer 
    - column: TotalAmount 
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 ConferenceBooking columns: 
    - column: Description 
    - column: ConferenceRoom 
    - column: Customer 
    - column: EndDateTime 
    - column: Title 
    - column: StartDateTime 
    - column: Status 
    - column: AttendeeCount 
    - column: CreatedAt 
The table should have the title "ConferenceBookings" und the data must be loaded from the server with the following relative URL: 
    "/CustomerService/conferencebooking/customer/{id}" 
Add a HTML table to the view with the following CustomerAddress columns: 
    - column: Country 
    - column: IsPrimary 
    - column: City 
    - column: PostalCode 
    - column: Label 
    - column: Customer 
    - column: Street 
The table should have the title "CustomerAddresss" und the data must be loaded from the server with the following relative URL: 
    "/CustomerService/customeraddress/customer/{id}"

4. The CustomerAddressView must contain the following fields: 
    - name: City   type: STRING 
    - name: Country   type: STRING 
    - name: Customer   type: Customer 
    - name: IsPrimary   type: BOOL 
    - name: Label   type: STRING 
    - name: PostalCode   type: STRING 
    - name: Street   type: STRING 
The data source for the [Customer] select control should be loaded from the relative URL: 
    "/CustomerService/customer"   (HTTP-GET) 
An existing CustomerAddress entity should be loaded from the relative URL: 
    "/CustomerService/customeraddress/{id}"   (HTTP-GET) 
If a new CustomerAddress entity has been created, the new entity should be posted to the relative URL: 
    "/CustomerService/customeraddress"   (HTTP-POST) 
If an existing CustomerAddress entity has been updated, the modified entity should be sent to the relative URL: 
    "/CustomerService/customeraddress/{id}"   (HTTP-PUT) 
If an existing CustomerAddress entity has to be deleted, the following relative URL should be called: 
    "/CustomerService/customeraddress/{id}"   (HTTP-DELETE)

5. The PaymentView must contain the following fields: 
    - name: Amount   type: STRING 
    - name: Booking   type: Booking 
    - name: CreatedAt   type: DATE 
    - name: Currency   type: STRING 
    - name: PaymentMethod   type: STRING 
    - name: PaymentStatus   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)