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. BookingParticipantView 
    3. CustomerView 
    4. EventRegistrationView 
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: BookingType   type: STRING 
    - name: Comment   type: STRING 
    - name: Court   type: Court 
    - name: CreatedAt   type: DATE 
    - name: Customer   type: Customer 
    - name: EndDateTime   type: DATE 
    - name: Source   type: STRING 
    - name: Sport   type: Sport 
    - name: StartDateTime   type: DATE 
    - name: Status   type: STRING 
The data source for the [Sport] select control should be loaded from the relative URL: 
    "/SportService/sport"   (HTTP-GET) 
The data source for the [Customer] select control should be loaded from the relative URL: 
    "/CustomerService/customer"   (HTTP-GET) 
The data source for the [Court] select control should be loaded from the relative URL: 
    "/CourtService/court"   (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 BookingParticipant columns: 
    - column: Booking 
    - column: IsMainPayer 
    - column: Customer 
    - column: GuestName 
The table should have the title "BookingParticipants" und the data must be loaded from the server with the following relative URL: 
    "/CustomerService/bookingparticipant/booking/{id}"

2. The BookingParticipantView must contain the following fields: 
    - name: Booking   type: Booking 
    - name: Customer   type: Customer 
    - name: GuestName   type: STRING 
    - name: IsMainPayer   type: BOOL 
The data source for the [Customer] select control should be loaded from the relative URL: 
    "/CustomerService/customer"   (HTTP-GET) 
The data source for the [Booking] select control should be loaded from the relative URL: 
    "/CustomerService/booking"   (HTTP-GET) 
An existing BookingParticipant entity should be loaded from the relative URL: 
    "/CustomerService/bookingparticipant/{id}"   (HTTP-GET) 
If a new BookingParticipant entity has been created, the new entity should be posted to the relative URL: 
    "/CustomerService/bookingparticipant"   (HTTP-POST) 
If an existing BookingParticipant entity has been updated, the modified entity should be sent to the relative URL: 
    "/CustomerService/bookingparticipant/{id}"   (HTTP-PUT) 
If an existing BookingParticipant entity has to be deleted, the following relative URL should be called: 
    "/CustomerService/bookingparticipant/{id}"   (HTTP-DELETE)

3. The CustomerView must contain the following fields: 
    - name: City   type: STRING 
    - name: Country   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: DateOfBirth   type: DATE 
    - name: Email   type: STRING 
    - name: FirstName   type: STRING 
    - name: LastName   type: STRING 
    - name: NewsletterOptIn   type: BOOL 
    - name: Phone   type: STRING 
    - name: PostalCode   type: STRING 
    - name: Street   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 ContactMessage columns: 
    - column: SourcePage 
    - column: MessageText 
    - column: Status 
    - column: Phone 
    - column: CreatedAt 
    - column: Customer 
    - column: Name 
    - column: Email 
    - column: Subject 
The table should have the title "ContactMessages" und the data must be loaded from the server with the following relative URL: 
    "/InvoiceService/contactmessage/customer/{id}" 
Add a HTML table to the view with the following Membership columns: 
    - column: AutoRenew 
    - column: EndDate 
    - column: StartDate 
    - column: CreatedAt 
    - column: MembershipType 
    - column: Customer 
    - column: Status 
The table should have the title "Memberships" und the data must be loaded from the server with the following relative URL: 
    "/MembershipTypeService/membership/customer/{id}" 
Add a HTML table to the view with the following Invoice columns: 
    - column: TotalGross 
    - column: CreatedAt 
    - column: Customer 
    - column: TaxAmount 
    - column: Status 
    - column: InvoiceDate 
    - column: TotalNet 
    - column: DueDate 
    - column: InvoiceNumber 
The table should have the title "Invoices" und the data must be loaded from the server with the following relative URL: 
    "/InvoiceService/invoice/customer/{id}" 
Add a HTML table to the view with the following BookingParticipant columns: 
    - column: Booking 
    - column: IsMainPayer 
    - column: Customer 
    - column: GuestName 
The table should have the title "BookingParticipants" und the data must be loaded from the server with the following relative URL: 
    "/CustomerService/bookingparticipant/customer/{id}" 
Add a HTML table to the view with the following TrainingParticipant columns: 
    - column: Role 
    - column: Customer 
    - column: TrainingSession 
    - column: RegisteredAt 
    - column: PriceOverride 
The table should have the title "TrainingParticipants" und the data must be loaded from the server with the following relative URL: 
    "/TrainingSessionService/trainingparticipant/customer/{id}" 
Add a HTML table to the view with the following EventRegistration columns: 
    - column: Status 
    - column: Customer 
    - column: RegisteredAt 
    - column: TeamName 
    - column: Comment 
    - column: Event 
The table should have the title "EventRegistrations" und the data must be loaded from the server with the following relative URL: 
    "/CustomerService/eventregistration/customer/{id}" 
Add a HTML table to the view with the following Booking columns: 
    - column: CreatedAt 
    - column: EndDateTime 
    - column: Customer 
    - column: BookingType 
    - column: Source 
    - column: Sport 
    - column: Court 
    - column: Status 
    - column: Comment 
    - column: StartDateTime 
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}"

4. The EventRegistrationView must contain the following fields: 
    - name: Comment   type: STRING 
    - name: Customer   type: Customer 
    - name: Event   type: Event 
    - name: RegisteredAt   type: DATE 
    - name: Status   type: STRING 
    - name: TeamName   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 [Event] select control should be loaded from the relative URL: 
    "/SportService/event"   (HTTP-GET) 
An existing EventRegistration entity should be loaded from the relative URL: 
    "/CustomerService/eventregistration/{id}"   (HTTP-GET) 
If a new EventRegistration entity has been created, the new entity should be posted to the relative URL: 
    "/CustomerService/eventregistration"   (HTTP-POST) 
If an existing EventRegistration entity has been updated, the modified entity should be sent to the relative URL: 
    "/CustomerService/eventregistration/{id}"   (HTTP-PUT) 
If an existing EventRegistration entity has to be deleted, the following relative URL should be called: 
    "/CustomerService/eventregistration/{id}"   (HTTP-DELETE)