Prompt for the EventApp

Please create a React-JS application for the EventModule. The application  has to offer the following views for the user interface: 
    1. BookingItemView 
    2. EventView 
    3. EventCategoryView 
    4. EventPerformerView 
    5. OrganizerView 
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 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: 
    "/VenueAreaService/seat"   (HTTP-GET) 
The data source for the [EventTicketType] select control should be loaded from the relative URL: 
    "/PriceCategoryService/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: 
    "/CustomerService/booking"   (HTTP-GET) 
An existing BookingItem entity should be loaded from the relative URL: 
    "/EventService/bookingitem/{id}"   (HTTP-GET) 
If a new BookingItem entity has been created, the new entity should be posted to the relative URL: 
    "/EventService/bookingitem"   (HTTP-POST) 
If an existing BookingItem entity has been updated, the modified entity should be sent to the relative URL: 
    "/EventService/bookingitem/{id}"   (HTTP-PUT) 
If an existing BookingItem entity has to be deleted, the following relative URL should be called: 
    "/EventService/bookingitem/{id}"   (HTTP-DELETE)

2. The EventView must contain the following fields: 
    - name: Arena   type: Arena 
    - name: Description   type: STRING 
    - name: DoorOpenTime   type: DATE 
    - name: EndDateTime   type: DATE 
    - name: EventCategory   type: EventCategory 
    - name: EventSeries   type: EventSeries 
    - name: ExternalReference   type: STRING 
    - name: IsCanceled   type: BOOL 
    - name: IsPostponed   type: BOOL 
    - name: Language   type: STRING 
    - name: MinimumAge   type: LONG 
    - name: Name   type: STRING 
    - name: Organizer   type: Organizer 
    - name: StartDateTime   type: DATE 
    - name: Subtitle   type: STRING 
    - name: TicketUrl   type: STRING 
    - name: VenueArea   type: VenueArea 
The data source for the [EventCategory] select control should be loaded from the relative URL: 
    "/EventService/eventcategory"   (HTTP-GET) 
The data source for the [Organizer] select control should be loaded from the relative URL: 
    "/EventService/organizer"   (HTTP-GET) 
The data source for the [EventSeries] select control should be loaded from the relative URL: 
    "/EventSeriesService/eventseries"   (HTTP-GET) 
The data source for the [VenueArea] select control should be loaded from the relative URL: 
    "/VenueAreaService/venuearea"   (HTTP-GET) 
The data source for the [Arena] select control should be loaded from the relative URL: 
    "/ArenaService/arena"   (HTTP-GET) 
An existing Event entity should be loaded from the relative URL: 
    "/EventService/event/{id}"   (HTTP-GET) 
If a new Event entity has been created, the new entity should be posted to the relative URL: 
    "/EventService/event"   (HTTP-POST) 
If an existing Event entity has been updated, the modified entity should be sent to the relative URL: 
    "/EventService/event/{id}"   (HTTP-PUT) 
If an existing Event entity has to be deleted, the following relative URL should be called: 
    "/EventService/event/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following NewsArticle columns: 
    - column: Event 
    - column: Teaser 
    - column: IsHighlighted 
    - column: Content 
    - column: Slug 
    - column: PublishedAt 
    - column: Title 
The table should have the title "NewsArticles" und the data must be loaded from the server with the following relative URL: 
    "/EventSeriesService/newsarticle/event/{id}" 
Add a HTML table to the view with the following SportsMatch columns: 
    - column: League 
    - column: Notes 
    - column: IsPenalty 
    - column: HomeScore 
    - column: MatchDay 
    - column: HomeTeam 
    - column: AwayTeam 
    - column: AwayScore 
    - column: IsOvertime 
    - column: Event 
The table should have the title "SportsMatchs" und the data must be loaded from the server with the following relative URL: 
    "/ArenaService/sportsmatch/event/{id}" 
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/event/{id}" 
Add a HTML table to the view with the following EventTicketType columns: 
    - column: VenueArea 
    - column: SoldQuantity 
    - column: TicketType 
    - column: SeatBlock 
    - column: IsActive 
    - column: TotalAllocation 
    - column: Event 
    - column: PriceCategory 
    - column: BasePrice 
The table should have the title "EventTicketTypes" und the data must be loaded from the server with the following relative URL: 
    "/PriceCategoryService/eventtickettype/event/{id}" 
Add a HTML table to the view with the following EventPerformer columns: 
    - column: DisplayOrder 
    - column: Role 
    - column: Performer 
    - column: Event 
The table should have the title "EventPerformers" und the data must be loaded from the server with the following relative URL: 
    "/EventService/eventperformer/event/{id}"

3. The EventCategoryView must contain the following fields: 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
An existing EventCategory entity should be loaded from the relative URL: 
    "/EventService/eventcategory/{id}"   (HTTP-GET) 
If a new EventCategory entity has been created, the new entity should be posted to the relative URL: 
    "/EventService/eventcategory"   (HTTP-POST) 
If an existing EventCategory entity has been updated, the modified entity should be sent to the relative URL: 
    "/EventService/eventcategory/{id}"   (HTTP-PUT) 
If an existing EventCategory entity has to be deleted, the following relative URL should be called: 
    "/EventService/eventcategory/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Event columns: 
    - column: ExternalReference 
    - column: TicketUrl 
    - column: DoorOpenTime 
    - column: StartDateTime 
    - column: Organizer 
    - column: EndDateTime 
    - column: Subtitle 
    - column: VenueArea 
    - column: Language 
    - column: Arena 
    - column: Name 
    - column: Description 
    - column: IsCanceled 
    - column: EventSeries 
    - column: IsPostponed 
    - column: EventCategory 
    - column: MinimumAge 
The table should have the title "Events" und the data must be loaded from the server with the following relative URL: 
    "/EventService/event/eventcategory/{id}"

4. The EventPerformerView must contain the following fields: 
    - name: DisplayOrder   type: LONG 
    - name: Event   type: Event 
    - name: Performer   type: Performer 
    - name: Role   type: STRING 
The data source for the [Performer] select control should be loaded from the relative URL: 
    "/PerformerService/performer"   (HTTP-GET) 
The data source for the [Event] select control should be loaded from the relative URL: 
    "/EventService/event"   (HTTP-GET) 
An existing EventPerformer entity should be loaded from the relative URL: 
    "/EventService/eventperformer/{id}"   (HTTP-GET) 
If a new EventPerformer entity has been created, the new entity should be posted to the relative URL: 
    "/EventService/eventperformer"   (HTTP-POST) 
If an existing EventPerformer entity has been updated, the modified entity should be sent to the relative URL: 
    "/EventService/eventperformer/{id}"   (HTTP-PUT) 
If an existing EventPerformer entity has to be deleted, the following relative URL should be called: 
    "/EventService/eventperformer/{id}"   (HTTP-DELETE)

5. The OrganizerView must contain the following fields: 
    - name: ContactEmail   type: STRING 
    - name: ContactPhone   type: STRING 
    - name: Name   type: STRING 
    - name: Notes   type: STRING 
    - name: WebsiteUrl   type: STRING 
An existing Organizer entity should be loaded from the relative URL: 
    "/EventService/organizer/{id}"   (HTTP-GET) 
If a new Organizer entity has been created, the new entity should be posted to the relative URL: 
    "/EventService/organizer"   (HTTP-POST) 
If an existing Organizer entity has been updated, the modified entity should be sent to the relative URL: 
    "/EventService/organizer/{id}"   (HTTP-PUT) 
If an existing Organizer entity has to be deleted, the following relative URL should be called: 
    "/EventService/organizer/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Event columns: 
    - column: ExternalReference 
    - column: TicketUrl 
    - column: DoorOpenTime 
    - column: StartDateTime 
    - column: Organizer 
    - column: EndDateTime 
    - column: Subtitle 
    - column: VenueArea 
    - column: Language 
    - column: Arena 
    - column: Name 
    - column: Description 
    - column: IsCanceled 
    - column: EventSeries 
    - column: IsPostponed 
    - column: EventCategory 
    - column: MinimumAge 
The table should have the title "Events" und the data must be loaded from the server with the following relative URL: 
    "/EventService/event/organizer/{id}"