Prompt for the SeatApp

Please create a React-JS application for the SeatModule. The application  has to offer the following views for the user interface: 
    1. BookingItemView 
    2. LegalDocumentView 
    3. SeatView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 3 views are defined below.

1. The BookingItemView must contain the following fields: 
    - name: Booking   type: Booking 
    - name: Event   type: Event 
    - name: EventTicketType   type: EventTicketType 
    - name: Quantity   type: LONG 
    - name: Seat   type: Seat 
    - name: TotalPrice   type: STRING 
    - name: UnitPrice   type: STRING 
The data source for the [Seat] select control should be loaded from the relative URL: 
    "/SeatService/seat"   (HTTP-GET) 
The data source for the [EventTicketType] select control should be loaded from the relative URL: 
    "/VenueAreaService/eventtickettype"   (HTTP-GET) 
The data source for the [Event] select control should be loaded from the relative URL: 
    "/EventService/event"   (HTTP-GET) 
The data source for the [Booking] select control should be loaded from the relative URL: 
    "/BookingService/booking"   (HTTP-GET) 
An existing BookingItem entity should be loaded from the relative URL: 
    "/SeatService/bookingitem/{id}"   (HTTP-GET) 
If a new BookingItem entity has been created, the new entity should be posted to the relative URL: 
    "/SeatService/bookingitem"   (HTTP-POST) 
If an existing BookingItem entity has been updated, the modified entity should be sent to the relative URL: 
    "/SeatService/bookingitem/{id}"   (HTTP-PUT) 
If an existing BookingItem entity has to be deleted, the following relative URL should be called: 
    "/SeatService/bookingitem/{id}"   (HTTP-DELETE)

2. The LegalDocumentView must contain the following fields: 
    - name: Content   type: STRING 
    - name: EffectiveFrom   type: DATE 
    - name: LastUpdated   type: DATE 
    - name: Slug   type: STRING 
    - name: Title   type: STRING 
    - name: VersionLabel   type: STRING 
An existing LegalDocument entity should be loaded from the relative URL: 
    "/SeatService/legaldocument/{id}"   (HTTP-GET) 
If a new LegalDocument entity has been created, the new entity should be posted to the relative URL: 
    "/SeatService/legaldocument"   (HTTP-POST) 
If an existing LegalDocument entity has been updated, the modified entity should be sent to the relative URL: 
    "/SeatService/legaldocument/{id}"   (HTTP-PUT) 
If an existing LegalDocument entity has to be deleted, the following relative URL should be called: 
    "/SeatService/legaldocument/{id}"   (HTTP-DELETE)

3. The SeatView must contain the following fields: 
    - name: IsStanding   type: BOOL 
    - name: RowLabel   type: STRING 
    - name: SeatBlock   type: SeatBlock 
    - name: SeatNumber   type: STRING 
The data source for the [SeatBlock] select control should be loaded from the relative URL: 
    "/VenueAreaService/seatblock"   (HTTP-GET) 
An existing Seat entity should be loaded from the relative URL: 
    "/SeatService/seat/{id}"   (HTTP-GET) 
If a new Seat entity has been created, the new entity should be posted to the relative URL: 
    "/SeatService/seat"   (HTTP-POST) 
If an existing Seat entity has been updated, the modified entity should be sent to the relative URL: 
    "/SeatService/seat/{id}"   (HTTP-PUT) 
If an existing Seat entity has to be deleted, the following relative URL should be called: 
    "/SeatService/seat/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following BookingItem columns: 
    - column: Quantity 
    - column: Booking 
    - column: EventTicketType 
    - column: UnitPrice 
    - column: Event 
    - column: Seat 
    - column: TotalPrice 
The table should have the title "BookingItems" und the data must be loaded from the server with the following relative URL: 
    "/SeatService/bookingitem/seat/{id}"