Prompt for the SportApp

Please create a React-JS application for the SportModule. The application  has to offer the following views for the user interface: 
    1. BookingView 
    2. CourtSportView 
    3. EventView 
    4. SportView 
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: 
    "/SportService/booking/{id}"   (HTTP-GET) 
If a new Booking entity has been created, the new entity should be posted to the relative URL: 
    "/SportService/booking"   (HTTP-POST) 
If an existing Booking entity has been updated, the modified entity should be sent to the relative URL: 
    "/SportService/booking/{id}"   (HTTP-PUT) 
If an existing Booking entity has to be deleted, the following relative URL should be called: 
    "/SportService/booking/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following BookingParticipant columns: 
    - column: GuestName 
    - column: Customer 
    - column: IsMainPayer 
    - column: Booking 
The table should have the title "BookingParticipants" und the data must be loaded from the server with the following relative URL: 
    "/CoachService/bookingparticipant/booking/{id}"

2. The CourtSportView must contain the following fields: 
    - name: Court   type: Court 
    - name: IsPrimary   type: BOOL 
    - name: Sport   type: Sport 
The data source for the [Sport] select control should be loaded from the relative URL: 
    "/SportService/sport"   (HTTP-GET) 
The data source for the [Court] select control should be loaded from the relative URL: 
    "/CourtService/court"   (HTTP-GET) 
An existing CourtSport entity should be loaded from the relative URL: 
    "/SportService/courtsport/{id}"   (HTTP-GET) 
If a new CourtSport entity has been created, the new entity should be posted to the relative URL: 
    "/SportService/courtsport"   (HTTP-POST) 
If an existing CourtSport entity has been updated, the modified entity should be sent to the relative URL: 
    "/SportService/courtsport/{id}"   (HTTP-PUT) 
If an existing CourtSport entity has to be deleted, the following relative URL should be called: 
    "/SportService/courtsport/{id}"   (HTTP-DELETE)

3. The EventView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: Description   type: STRING 
    - name: EndDateTime   type: DATE 
    - name: LocationText   type: STRING 
    - name: MaxParticipants   type: LONG 
    - name: Name   type: STRING 
    - name: PublicVisible   type: BOOL 
    - name: RegistrationDeadline   type: DATE 
    - 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) 
An existing Event entity should be loaded from the relative URL: 
    "/SportService/event/{id}"   (HTTP-GET) 
If a new Event entity has been created, the new entity should be posted to the relative URL: 
    "/SportService/event"   (HTTP-POST) 
If an existing Event entity has been updated, the modified entity should be sent to the relative URL: 
    "/SportService/event/{id}"   (HTTP-PUT) 
If an existing Event entity has to be deleted, the following relative URL should be called: 
    "/SportService/event/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following EventRegistration columns: 
    - column: TeamName 
    - column: Comment 
    - column: RegisteredAt 
    - column: Status 
    - column: Event 
    - column: Customer 
The table should have the title "EventRegistrations" und the data must be loaded from the server with the following relative URL: 
    "/CustomerService/eventregistration/event/{id}"

4. The SportView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: Description   type: STRING 
    - name: IsActive   type: BOOL 
    - name: Name   type: STRING 
An existing Sport entity should be loaded from the relative URL: 
    "/SportService/sport/{id}"   (HTTP-GET) 
If a new Sport entity has been created, the new entity should be posted to the relative URL: 
    "/SportService/sport"   (HTTP-POST) 
If an existing Sport entity has been updated, the modified entity should be sent to the relative URL: 
    "/SportService/sport/{id}"   (HTTP-PUT) 
If an existing Sport entity has to be deleted, the following relative URL should be called: 
    "/SportService/sport/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following TrainingOffer columns: 
    - column: Level 
    - column: Description 
    - column: IsActive 
    - column: GroupSizeMax 
    - column: GroupSizeMin 
    - column: Sport 
    - column: DefaultPrice 
    - column: CreatedAt 
    - column: Name 
    - column: DurationMinutes 
The table should have the title "TrainingOffers" und the data must be loaded from the server with the following relative URL: 
    "/CoachService/trainingoffer/sport/{id}" 
Add a HTML table to the view with the following Event columns: 
    - column: EndDateTime 
    - column: Status 
    - column: Name 
    - column: Sport 
    - column: LocationText 
    - column: MaxParticipants 
    - column: PublicVisible 
    - column: Description 
    - column: RegistrationDeadline 
    - column: StartDateTime 
    - column: CreatedAt 
The table should have the title "Events" und the data must be loaded from the server with the following relative URL: 
    "/SportService/event/sport/{id}" 
Add a HTML table to the view with the following PriceItem columns: 
    - column: MembershipType 
    - column: PriceList 
    - column: Sport 
    - column: CreatedAt 
    - column: TimeFrom 
    - column: PricePerHour 
    - column: TimeTo 
    - column: DayOfWeek 
    - column: BookingType 
The table should have the title "PriceItems" und the data must be loaded from the server with the following relative URL: 
    "/MembershipTypeService/priceitem/sport/{id}" 
Add a HTML table to the view with the following Booking columns: 
    - column: BookingType 
    - column: Court 
    - column: EndDateTime 
    - column: Status 
    - column: Source 
    - column: Comment 
    - column: CreatedAt 
    - column: StartDateTime 
    - column: Customer 
    - column: Sport 
The table should have the title "Bookings" und the data must be loaded from the server with the following relative URL: 
    "/SportService/booking/sport/{id}" 
Add a HTML table to the view with the following CourtSport columns: 
    - column: Court 
    - column: IsPrimary 
    - column: Sport 
The table should have the title "CourtSports" und the data must be loaded from the server with the following relative URL: 
    "/SportService/courtsport/sport/{id}"