Prompt for the UserRoleApp

Please create a React-JS application for the UserRoleModule. The application  has to offer the following views for the user interface: 
    1. DeveloperApplicationView 
    2. UserAccountRoleView 
    3. UserRoleView 
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 DeveloperApplicationView must contain the following fields: 
    - name: ApiKey   type: STRING 
    - name: CreatedDate   type: DATE 
    - name: Name   type: STRING 
    - name: OwnerUserAccount   type: UserAccount 
    - name: Status   type: STRING 
The data source for the [OwnerUserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing DeveloperApplication entity should be loaded from the relative URL: 
    "/UserRoleService/developerapplication/{id}"   (HTTP-GET) 
If a new DeveloperApplication entity has been created, the new entity should be posted to the relative URL: 
    "/UserRoleService/developerapplication"   (HTTP-POST) 
If an existing DeveloperApplication entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserRoleService/developerapplication/{id}"   (HTTP-PUT) 
If an existing DeveloperApplication entity has to be deleted, the following relative URL should be called: 
    "/UserRoleService/developerapplication/{id}"   (HTTP-DELETE)

2. The UserAccountRoleView must contain the following fields: 
    - name: AssignedDate   type: DATE 
    - name: UserAccount   type: UserAccount 
    - name: UserRole   type: UserRole 
The data source for the [UserRole] select control should be loaded from the relative URL: 
    "/UserRoleService/userrole"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing UserAccountRole entity should be loaded from the relative URL: 
    "/UserRoleService/useraccountrole/{id}"   (HTTP-GET) 
If a new UserAccountRole entity has been created, the new entity should be posted to the relative URL: 
    "/UserRoleService/useraccountrole"   (HTTP-POST) 
If an existing UserAccountRole entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserRoleService/useraccountrole/{id}"   (HTTP-PUT) 
If an existing UserAccountRole entity has to be deleted, the following relative URL should be called: 
    "/UserRoleService/useraccountrole/{id}"   (HTTP-DELETE)

3. The UserRoleView must contain the following fields: 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
An existing UserRole entity should be loaded from the relative URL: 
    "/UserRoleService/userrole/{id}"   (HTTP-GET) 
If a new UserRole entity has been created, the new entity should be posted to the relative URL: 
    "/UserRoleService/userrole"   (HTTP-POST) 
If an existing UserRole entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserRoleService/userrole/{id}"   (HTTP-PUT) 
If an existing UserRole entity has to be deleted, the following relative URL should be called: 
    "/UserRoleService/userrole/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following UserAccountRole columns: 
    - column: UserAccount 
    - column: AssignedDate 
    - column: UserRole 
The table should have the title "UserAccountRoles" und the data must be loaded from the server with the following relative URL: 
    "/UserRoleService/useraccountrole/userrole/{id}"