Prompt for the GameApp

Please create a React-JS application for the GameModule. The application  has to offer the following views for the user interface: 
    1. GameView 
    2. GameSessionView 
    3. NotificationView 
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 GameView must contain the following fields: 
    - name: Category   type: STRING 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
    - name: Url   type: STRING 
An existing Game entity should be loaded from the relative URL: 
    "/GameService/game/{id}"   (HTTP-GET) 
If a new Game entity has been created, the new entity should be posted to the relative URL: 
    "/GameService/game"   (HTTP-POST) 
If an existing Game entity has been updated, the modified entity should be sent to the relative URL: 
    "/GameService/game/{id}"   (HTTP-PUT) 
If an existing Game entity has to be deleted, the following relative URL should be called: 
    "/GameService/game/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following GameSession columns: 
    - column: Score 
    - column: User 
    - column: Game 
    - column: StartedAt 
    - column: EndedAt 
The table should have the title "GameSessions" und the data must be loaded from the server with the following relative URL: 
    "/GameService/gamesession/game/{id}"

2. The GameSessionView must contain the following fields: 
    - name: EndedAt   type: DATE 
    - name: Game   type: Game 
    - name: Score   type: INT 
    - name: StartedAt   type: DATE 
    - name: User   type: UserAccount 
The data source for the [Game] select control should be loaded from the relative URL: 
    "/GameService/game"   (HTTP-GET) 
The data source for the [User] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing GameSession entity should be loaded from the relative URL: 
    "/GameService/gamesession/{id}"   (HTTP-GET) 
If a new GameSession entity has been created, the new entity should be posted to the relative URL: 
    "/GameService/gamesession"   (HTTP-POST) 
If an existing GameSession entity has been updated, the modified entity should be sent to the relative URL: 
    "/GameService/gamesession/{id}"   (HTTP-PUT) 
If an existing GameSession entity has to be deleted, the following relative URL should be called: 
    "/GameService/gamesession/{id}"   (HTTP-DELETE)

3. The NotificationView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: DataJson   type: STRING 
    - name: IsRead   type: BOOL 
    - name: Type   type: STRING 
    - name: User   type: UserAccount 
The data source for the [User] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing Notification entity should be loaded from the relative URL: 
    "/GameService/notification/{id}"   (HTTP-GET) 
If a new Notification entity has been created, the new entity should be posted to the relative URL: 
    "/GameService/notification"   (HTTP-POST) 
If an existing Notification entity has been updated, the modified entity should be sent to the relative URL: 
    "/GameService/notification/{id}"   (HTTP-PUT) 
If an existing Notification entity has to be deleted, the following relative URL should be called: 
    "/GameService/notification/{id}"   (HTTP-DELETE)