Prompt for the PerformerApp

Please create a React-JS application for the PerformerModule. The application  has to offer the following views for the user interface: 
    1. NavigationItemView 
    2. PageView 
    3. PerformerView 
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 NavigationItemView must contain the following fields: 
    - name: DisplayOrder   type: LONG 
    - name: IsVisible   type: BOOL 
    - name: Label   type: STRING 
    - name: Page   type: Page 
    - name: ParentItem   type: LONG 
    - name: Url   type: STRING 
The data source for the [Page] select control should be loaded from the relative URL: 
    "/PerformerService/page"   (HTTP-GET) 
An existing NavigationItem entity should be loaded from the relative URL: 
    "/PerformerService/navigationitem/{id}"   (HTTP-GET) 
If a new NavigationItem entity has been created, the new entity should be posted to the relative URL: 
    "/PerformerService/navigationitem"   (HTTP-POST) 
If an existing NavigationItem entity has been updated, the modified entity should be sent to the relative URL: 
    "/PerformerService/navigationitem/{id}"   (HTTP-PUT) 
If an existing NavigationItem entity has to be deleted, the following relative URL should be called: 
    "/PerformerService/navigationitem/{id}"   (HTTP-DELETE)

2. The PageView must contain the following fields: 
    - name: Content   type: STRING 
    - name: IsPublished   type: BOOL 
    - name: MetaDescription   type: STRING 
    - name: Slug   type: STRING 
    - name: Title   type: STRING 
An existing Page entity should be loaded from the relative URL: 
    "/PerformerService/page/{id}"   (HTTP-GET) 
If a new Page entity has been created, the new entity should be posted to the relative URL: 
    "/PerformerService/page"   (HTTP-POST) 
If an existing Page entity has been updated, the modified entity should be sent to the relative URL: 
    "/PerformerService/page/{id}"   (HTTP-PUT) 
If an existing Page entity has to be deleted, the following relative URL should be called: 
    "/PerformerService/page/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following NavigationItem columns: 
    - column: IsVisible 
    - column: Page 
    - column: Label 
    - column: ParentItem 
    - column: DisplayOrder 
    - column: Url 
The table should have the title "NavigationItems" und the data must be loaded from the server with the following relative URL: 
    "/PerformerService/navigationitem/page/{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: 
    "/PerformerService/performer/{id}"   (HTTP-GET) 
If a new Performer entity has been created, the new entity should be posted to the relative URL: 
    "/PerformerService/performer"   (HTTP-POST) 
If an existing Performer entity has been updated, the modified entity should be sent to the relative URL: 
    "/PerformerService/performer/{id}"   (HTTP-PUT) 
If an existing Performer entity has to be deleted, the following relative URL should be called: 
    "/PerformerService/performer/{id}"   (HTTP-DELETE) 
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/performer/{id}"