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. ArenaView 
    2. EventView 
    3. NewsArticleView 
    4. SportsLeagueView 
    5. SportsMatchView 
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 ArenaView must contain the following fields: 
    - name: Address   type: STRING 
    - name: City   type: STRING 
    - name: Country   type: STRING 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
    - name: OpenedDate   type: DATE 
    - name: PostalCode   type: STRING 
    - name: WebsiteUrl   type: STRING 
An existing Arena entity should be loaded from the relative URL: 
    "/EventService/arena/{id}"   (HTTP-GET) 
If a new Arena entity has been created, the new entity should be posted to the relative URL: 
    "/EventService/arena"   (HTTP-POST) 
If an existing Arena entity has been updated, the modified entity should be sent to the relative URL: 
    "/EventService/arena/{id}"   (HTTP-PUT) 
If an existing Arena entity has to be deleted, the following relative URL should be called: 
    "/EventService/arena/{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/arena/{id}" 
Add a HTML table to the view with the following SportsTeam columns: 
    - column: IsHomeTeam 
    - column: WebsiteUrl 
    - column: City 
    - column: Name 
    - column: HomeArena 
    - column: ShortName 
    - column: Country 
The table should have the title "SportsTeams" und the data must be loaded from the server with the following relative URL: 
    "/SportsTeamService/sportsteam/homearena/{id}" 
Add a HTML table to the view with the following VenueArea columns: 
    - column: Arena 
    - column: Type 
    - column: Name 
    - column: Description 
    - column: Capacity 
The table should have the title "VenueAreas" und the data must be loaded from the server with the following relative URL: 
    "/VenueAreaService/venuearea/arena/{id}"

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: 
    "/PageService/eventcategory"   (HTTP-GET) 
The data source for the [Organizer] select control should be loaded from the relative URL: 
    "/OrganizerService/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: 
    "/EventService/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 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/event/{id}" 
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/event/{id}" 
Add a HTML table to the view with the following NewsArticle columns: 
    - column: Teaser 
    - column: PublishedAt 
    - column: Event 
    - column: Title 
    - column: Content 
    - column: Slug 
    - column: IsHighlighted 
The table should have the title "NewsArticles" und the data must be loaded from the server with the following relative URL: 
    "/EventService/newsarticle/event/{id}" 
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/event/{id}" 
Add a HTML table to the view with the following SportsMatch columns: 
    - column: HomeTeam 
    - column: MatchDay 
    - column: Event 
    - column: AwayTeam 
    - column: League 
    - column: IsPenalty 
    - column: AwayScore 
    - column: IsOvertime 
    - column: HomeScore 
    - column: Notes 
The table should have the title "SportsMatchs" und the data must be loaded from the server with the following relative URL: 
    "/EventService/sportsmatch/event/{id}"

3. The NewsArticleView must contain the following fields: 
    - name: Content   type: STRING 
    - name: Event   type: Event 
    - name: IsHighlighted   type: BOOL 
    - name: PublishedAt   type: DATE 
    - name: Slug   type: STRING 
    - name: Teaser   type: STRING 
    - name: Title   type: STRING 
The data source for the [Event] select control should be loaded from the relative URL: 
    "/EventService/event"   (HTTP-GET) 
An existing NewsArticle entity should be loaded from the relative URL: 
    "/EventService/newsarticle/{id}"   (HTTP-GET) 
If a new NewsArticle entity has been created, the new entity should be posted to the relative URL: 
    "/EventService/newsarticle"   (HTTP-POST) 
If an existing NewsArticle entity has been updated, the modified entity should be sent to the relative URL: 
    "/EventService/newsarticle/{id}"   (HTTP-PUT) 
If an existing NewsArticle entity has to be deleted, the following relative URL should be called: 
    "/EventService/newsarticle/{id}"   (HTTP-DELETE)

4. The SportsLeagueView must contain the following fields: 
    - name: Country   type: STRING 
    - name: Level   type: STRING 
    - name: Name   type: STRING 
    - name: Sport   type: STRING 
An existing SportsLeague entity should be loaded from the relative URL: 
    "/EventService/sportsleague/{id}"   (HTTP-GET) 
If a new SportsLeague entity has been created, the new entity should be posted to the relative URL: 
    "/EventService/sportsleague"   (HTTP-POST) 
If an existing SportsLeague entity has been updated, the modified entity should be sent to the relative URL: 
    "/EventService/sportsleague/{id}"   (HTTP-PUT) 
If an existing SportsLeague entity has to be deleted, the following relative URL should be called: 
    "/EventService/sportsleague/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following SportsMatch columns: 
    - column: HomeTeam 
    - column: MatchDay 
    - column: Event 
    - column: AwayTeam 
    - column: League 
    - column: IsPenalty 
    - column: AwayScore 
    - column: IsOvertime 
    - column: HomeScore 
    - column: Notes 
The table should have the title "SportsMatchs" und the data must be loaded from the server with the following relative URL: 
    "/EventService/sportsmatch/league/{id}"

5. The SportsMatchView must contain the following fields: 
    - name: AwayScore   type: LONG 
    - name: AwayTeam   type: SportsTeam 
    - name: Event   type: Event 
    - name: HomeScore   type: LONG 
    - name: HomeTeam   type: SportsTeam 
    - name: IsOvertime   type: BOOL 
    - name: IsPenalty   type: BOOL 
    - name: League   type: SportsLeague 
    - name: MatchDay   type: LONG 
    - name: Notes   type: STRING 
The data source for the [League] select control should be loaded from the relative URL: 
    "/EventService/sportsleague"   (HTTP-GET) 
The data source for the [AwayTeam] select control should be loaded from the relative URL: 
    "/SportsTeamService/sportsteam"   (HTTP-GET) 
The data source for the [HomeTeam] select control should be loaded from the relative URL: 
    "/SportsTeamService/sportsteam"   (HTTP-GET) 
The data source for the [Event] select control should be loaded from the relative URL: 
    "/EventService/event"   (HTTP-GET) 
An existing SportsMatch entity should be loaded from the relative URL: 
    "/EventService/sportsmatch/{id}"   (HTTP-GET) 
If a new SportsMatch entity has been created, the new entity should be posted to the relative URL: 
    "/EventService/sportsmatch"   (HTTP-POST) 
If an existing SportsMatch entity has been updated, the modified entity should be sent to the relative URL: 
    "/EventService/sportsmatch/{id}"   (HTTP-PUT) 
If an existing SportsMatch entity has to be deleted, the following relative URL should be called: 
    "/EventService/sportsmatch/{id}"   (HTTP-DELETE)