Prompt for the EventSeriesApp

Please create a React-JS application for the EventSeriesModule. The application  has to offer the following views for the user interface: 
    1. EventPerformerView 
    2. EventSeriesView 
    3. PerformerView 
    4. TicketTypeView 
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 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: 
    "/EventSeriesService/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: 
    "/EventSeriesService/eventperformer/{id}"   (HTTP-GET) 
If a new EventPerformer entity has been created, the new entity should be posted to the relative URL: 
    "/EventSeriesService/eventperformer"   (HTTP-POST) 
If an existing EventPerformer entity has been updated, the modified entity should be sent to the relative URL: 
    "/EventSeriesService/eventperformer/{id}"   (HTTP-PUT) 
If an existing EventPerformer entity has to be deleted, the following relative URL should be called: 
    "/EventSeriesService/eventperformer/{id}"   (HTTP-DELETE)

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

3. The PerformerView must contain the following fields: 
    - name: Country   type: STRING 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
    - name: Type   type: STRING 
    - name: WebsiteUrl   type: STRING 
An existing Performer entity should be loaded from the relative URL: 
    "/EventSeriesService/performer/{id}"   (HTTP-GET) 
If a new Performer entity has been created, the new entity should be posted to the relative URL: 
    "/EventSeriesService/performer"   (HTTP-POST) 
If an existing Performer entity has been updated, the modified entity should be sent to the relative URL: 
    "/EventSeriesService/performer/{id}"   (HTTP-PUT) 
If an existing Performer entity has to be deleted, the following relative URL should be called: 
    "/EventSeriesService/performer/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following EventPerformer columns: 
    - column: DisplayOrder 
    - column: Event 
    - column: Performer 
    - column: Role 
The table should have the title "EventPerformers" und the data must be loaded from the server with the following relative URL: 
    "/EventSeriesService/eventperformer/performer/{id}"

4. The TicketTypeView must contain the following fields: 
    - name: Description   type: STRING 
    - name: IsSeated   type: BOOL 
    - name: Name   type: STRING 
An existing TicketType entity should be loaded from the relative URL: 
    "/EventSeriesService/tickettype/{id}"   (HTTP-GET) 
If a new TicketType entity has been created, the new entity should be posted to the relative URL: 
    "/EventSeriesService/tickettype"   (HTTP-POST) 
If an existing TicketType entity has been updated, the modified entity should be sent to the relative URL: 
    "/EventSeriesService/tickettype/{id}"   (HTTP-PUT) 
If an existing TicketType entity has to be deleted, the following relative URL should be called: 
    "/EventSeriesService/tickettype/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following EventTicketType columns: 
    - column: Event 
    - column: BasePrice 
    - column: IsActive 
    - column: SoldQuantity 
    - column: VenueArea 
    - column: TicketType 
    - column: TotalAllocation 
    - column: PriceCategory 
    - column: SeatBlock 
The table should have the title "EventTicketTypes" und the data must be loaded from the server with the following relative URL: 
    "/VenueAreaService/eventtickettype/tickettype/{id}"