Prompt for the CoachApp

Please create a React-JS application for the CoachModule. The application  has to offer the following views for the user interface: 
    1. BookingParticipantView 
    2. CoachView 
    3. TrainingOfferView 
    4. TrainingSessionView 
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 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: 
    "/SportService/booking"   (HTTP-GET) 
An existing BookingParticipant entity should be loaded from the relative URL: 
    "/CoachService/bookingparticipant/{id}"   (HTTP-GET) 
If a new BookingParticipant entity has been created, the new entity should be posted to the relative URL: 
    "/CoachService/bookingparticipant"   (HTTP-POST) 
If an existing BookingParticipant entity has been updated, the modified entity should be sent to the relative URL: 
    "/CoachService/bookingparticipant/{id}"   (HTTP-PUT) 
If an existing BookingParticipant entity has to be deleted, the following relative URL should be called: 
    "/CoachService/bookingparticipant/{id}"   (HTTP-DELETE)

2. The CoachView must contain the following fields: 
    - name: ActiveSince   type: DATE 
    - name: CreatedAt   type: DATE 
    - name: Email   type: STRING 
    - name: FirstName   type: STRING 
    - name: IsActive   type: BOOL 
    - name: IsExternal   type: BOOL 
    - name: LastName   type: STRING 
    - name: Phone   type: STRING 
    - name: ShortBio   type: STRING 
An existing Coach entity should be loaded from the relative URL: 
    "/CoachService/coach/{id}"   (HTTP-GET) 
If a new Coach entity has been created, the new entity should be posted to the relative URL: 
    "/CoachService/coach"   (HTTP-POST) 
If an existing Coach entity has been updated, the modified entity should be sent to the relative URL: 
    "/CoachService/coach/{id}"   (HTTP-PUT) 
If an existing Coach entity has to be deleted, the following relative URL should be called: 
    "/CoachService/coach/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following TrainingSession columns: 
    - column: Status 
    - column: CreatedAt 
    - column: EndDateTime 
    - column: Court 
    - column: Coach 
    - column: StartDateTime 
    - column: TrainingOffer 
    - column: MaxParticipants 
The table should have the title "TrainingSessions" und the data must be loaded from the server with the following relative URL: 
    "/CoachService/trainingsession/coach/{id}"

3. The TrainingOfferView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: DefaultPrice   type: STRING 
    - name: Description   type: STRING 
    - name: DurationMinutes   type: LONG 
    - name: GroupSizeMax   type: LONG 
    - name: GroupSizeMin   type: LONG 
    - name: IsActive   type: BOOL 
    - name: Level   type: STRING 
    - name: Name   type: STRING 
    - name: Sport   type: Sport 
The data source for the [Sport] select control should be loaded from the relative URL: 
    "/SportService/sport"   (HTTP-GET) 
An existing TrainingOffer entity should be loaded from the relative URL: 
    "/CoachService/trainingoffer/{id}"   (HTTP-GET) 
If a new TrainingOffer entity has been created, the new entity should be posted to the relative URL: 
    "/CoachService/trainingoffer"   (HTTP-POST) 
If an existing TrainingOffer entity has been updated, the modified entity should be sent to the relative URL: 
    "/CoachService/trainingoffer/{id}"   (HTTP-PUT) 
If an existing TrainingOffer entity has to be deleted, the following relative URL should be called: 
    "/CoachService/trainingoffer/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following TrainingSession columns: 
    - column: Status 
    - column: CreatedAt 
    - column: EndDateTime 
    - column: Court 
    - column: Coach 
    - column: StartDateTime 
    - column: TrainingOffer 
    - column: MaxParticipants 
The table should have the title "TrainingSessions" und the data must be loaded from the server with the following relative URL: 
    "/CoachService/trainingsession/trainingoffer/{id}"

4. The TrainingSessionView must contain the following fields: 
    - name: Coach   type: Coach 
    - name: Court   type: Court 
    - name: CreatedAt   type: DATE 
    - name: EndDateTime   type: DATE 
    - name: MaxParticipants   type: LONG 
    - name: StartDateTime   type: DATE 
    - name: Status   type: STRING 
    - name: TrainingOffer   type: TrainingOffer 
The data source for the [Coach] select control should be loaded from the relative URL: 
    "/CoachService/coach"   (HTTP-GET) 
The data source for the [Court] select control should be loaded from the relative URL: 
    "/CourtService/court"   (HTTP-GET) 
The data source for the [TrainingOffer] select control should be loaded from the relative URL: 
    "/CoachService/trainingoffer"   (HTTP-GET) 
An existing TrainingSession entity should be loaded from the relative URL: 
    "/CoachService/trainingsession/{id}"   (HTTP-GET) 
If a new TrainingSession entity has been created, the new entity should be posted to the relative URL: 
    "/CoachService/trainingsession"   (HTTP-POST) 
If an existing TrainingSession entity has been updated, the modified entity should be sent to the relative URL: 
    "/CoachService/trainingsession/{id}"   (HTTP-PUT) 
If an existing TrainingSession entity has to be deleted, the following relative URL should be called: 
    "/CoachService/trainingsession/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following TrainingParticipant columns: 
    - column: RegisteredAt 
    - column: TrainingSession 
    - column: Customer 
    - column: PriceOverride 
    - column: Role 
The table should have the title "TrainingParticipants" und the data must be loaded from the server with the following relative URL: 
    "/CustomerService/trainingparticipant/trainingsession/{id}"