Prompt for the EsportsPlayerApp

Please create a React-JS application for the EsportsPlayerModule. The application  has to offer the following views for the user interface: 
    1. EsportsMembershipView 
    2. EsportsPlayerView 
    3. EsportsTeamView 
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 EsportsMembershipView must contain the following fields: 
    - name: EsportsPlayer   type: EsportsPlayer 
    - name: EsportsTeam   type: EsportsTeam 
    - name: JoinDate   type: DATE 
    - name: LeaveDate   type: DATE 
    - name: Role   type: STRING 
The data source for the [EsportsPlayer] select control should be loaded from the relative URL: 
    "/EsportsPlayerService/esportsplayer"   (HTTP-GET) 
The data source for the [EsportsTeam] select control should be loaded from the relative URL: 
    "/EsportsPlayerService/esportsteam"   (HTTP-GET) 
An existing EsportsMembership entity should be loaded from the relative URL: 
    "/EsportsPlayerService/esportsmembership/{id}"   (HTTP-GET) 
If a new EsportsMembership entity has been created, the new entity should be posted to the relative URL: 
    "/EsportsPlayerService/esportsmembership"   (HTTP-POST) 
If an existing EsportsMembership entity has been updated, the modified entity should be sent to the relative URL: 
    "/EsportsPlayerService/esportsmembership/{id}"   (HTTP-PUT) 
If an existing EsportsMembership entity has to be deleted, the following relative URL should be called: 
    "/EsportsPlayerService/esportsmembership/{id}"   (HTTP-DELETE)

2. The EsportsPlayerView must contain the following fields: 
    - name: BirthYear   type: LONG 
    - name: Country   type: STRING 
    - name: GamerTag   type: STRING 
    - name: RealName   type: STRING 
An existing EsportsPlayer entity should be loaded from the relative URL: 
    "/EsportsPlayerService/esportsplayer/{id}"   (HTTP-GET) 
If a new EsportsPlayer entity has been created, the new entity should be posted to the relative URL: 
    "/EsportsPlayerService/esportsplayer"   (HTTP-POST) 
If an existing EsportsPlayer entity has been updated, the modified entity should be sent to the relative URL: 
    "/EsportsPlayerService/esportsplayer/{id}"   (HTTP-PUT) 
If an existing EsportsPlayer entity has to be deleted, the following relative URL should be called: 
    "/EsportsPlayerService/esportsplayer/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following EsportsMembership columns: 
    - column: JoinDate 
    - column: EsportsPlayer 
    - column: Role 
    - column: EsportsTeam 
    - column: LeaveDate 
The table should have the title "EsportsMemberships" und the data must be loaded from the server with the following relative URL: 
    "/EsportsPlayerService/esportsmembership/esportsplayer/{id}"

3. The EsportsTeamView must contain the following fields: 
    - name: Company   type: Company 
    - name: FoundedDate   type: DATE 
    - name: GameTitle   type: STRING 
    - name: Name   type: STRING 
    - name: Region   type: STRING 
The data source for the [Company] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
An existing EsportsTeam entity should be loaded from the relative URL: 
    "/EsportsPlayerService/esportsteam/{id}"   (HTTP-GET) 
If a new EsportsTeam entity has been created, the new entity should be posted to the relative URL: 
    "/EsportsPlayerService/esportsteam"   (HTTP-POST) 
If an existing EsportsTeam entity has been updated, the modified entity should be sent to the relative URL: 
    "/EsportsPlayerService/esportsteam/{id}"   (HTTP-PUT) 
If an existing EsportsTeam entity has to be deleted, the following relative URL should be called: 
    "/EsportsPlayerService/esportsteam/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following EsportsMembership columns: 
    - column: JoinDate 
    - column: EsportsPlayer 
    - column: Role 
    - column: EsportsTeam 
    - column: LeaveDate 
The table should have the title "EsportsMemberships" und the data must be loaded from the server with the following relative URL: 
    "/EsportsPlayerService/esportsmembership/esportsteam/{id}"