Prompt for the AppApp

Please create a React-JS application for the AppModule. The application  has to offer the following views for the user interface: 
    1. AppView 
    2. AppCategoryView 
    3. AppCategoryAssignmentView 
    4. MerchantView 
    5. MerchantAppInstallationView 
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 AppView must contain the following fields: 
    - name: AppStoreListingUrl   type: STRING 
    - name: Description   type: STRING 
    - name: DeveloperCompany   type: Company 
    - name: InitialReleaseDate   type: DATE 
    - name: IsShopifyOwned   type: BOOL 
    - name: Name   type: STRING 
The data source for the [DeveloperCompany] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
An existing App entity should be loaded from the relative URL: 
    "/AppService/app/{id}"   (HTTP-GET) 
If a new App entity has been created, the new entity should be posted to the relative URL: 
    "/AppService/app"   (HTTP-POST) 
If an existing App entity has been updated, the modified entity should be sent to the relative URL: 
    "/AppService/app/{id}"   (HTTP-PUT) 
If an existing App entity has to be deleted, the following relative URL should be called: 
    "/AppService/app/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following AppCategoryAssignment columns: 
    - column: App 
    - column: AppCategory 
The table should have the title "AppCategoryAssignments" und the data must be loaded from the server with the following relative URL: 
    "/AppService/appcategoryassignment/app/{id}" 
Add a HTML table to the view with the following MerchantAppInstallation columns: 
    - column: App 
    - column: Merchant 
    - column: InstallDate 
    - column: UninstallDate 
    - column: MonthlyRevenueShareUsd 
The table should have the title "MerchantAppInstallations" und the data must be loaded from the server with the following relative URL: 
    "/AppService/merchantappinstallation/app/{id}"

2. The AppCategoryView must contain the following fields: 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
An existing AppCategory entity should be loaded from the relative URL: 
    "/AppService/appcategory/{id}"   (HTTP-GET) 
If a new AppCategory entity has been created, the new entity should be posted to the relative URL: 
    "/AppService/appcategory"   (HTTP-POST) 
If an existing AppCategory entity has been updated, the modified entity should be sent to the relative URL: 
    "/AppService/appcategory/{id}"   (HTTP-PUT) 
If an existing AppCategory entity has to be deleted, the following relative URL should be called: 
    "/AppService/appcategory/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following AppCategoryAssignment columns: 
    - column: App 
    - column: AppCategory 
The table should have the title "AppCategoryAssignments" und the data must be loaded from the server with the following relative URL: 
    "/AppService/appcategoryassignment/appcategory/{id}"

3. The AppCategoryAssignmentView must contain the following fields: 
    - name: App   type: App 
    - name: AppCategory   type: AppCategory 
The data source for the [App] select control should be loaded from the relative URL: 
    "/AppService/app"   (HTTP-GET) 
The data source for the [AppCategory] select control should be loaded from the relative URL: 
    "/AppService/appcategory"   (HTTP-GET) 
An existing AppCategoryAssignment entity should be loaded from the relative URL: 
    "/AppService/appcategoryassignment/{id}"   (HTTP-GET) 
If a new AppCategoryAssignment entity has been created, the new entity should be posted to the relative URL: 
    "/AppService/appcategoryassignment"   (HTTP-POST) 
If an existing AppCategoryAssignment entity has been updated, the modified entity should be sent to the relative URL: 
    "/AppService/appcategoryassignment/{id}"   (HTTP-PUT) 
If an existing AppCategoryAssignment entity has to be deleted, the following relative URL should be called: 
    "/AppService/appcategoryassignment/{id}"   (HTTP-DELETE)

4. The MerchantView must contain the following fields: 
    - name: Company   type: Company 
    - name: Country   type: STRING 
    - name: Industry   type: STRING 
    - name: IsActive   type: BOOL 
    - name: IsShopifyPlus   type: BOOL 
    - name: MerchantSize   type: STRING 
    - name: OnboardingDate   type: DATE 
The data source for the [Company] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
An existing Merchant entity should be loaded from the relative URL: 
    "/AppService/merchant/{id}"   (HTTP-GET) 
If a new Merchant entity has been created, the new entity should be posted to the relative URL: 
    "/AppService/merchant"   (HTTP-POST) 
If an existing Merchant entity has been updated, the modified entity should be sent to the relative URL: 
    "/AppService/merchant/{id}"   (HTTP-PUT) 
If an existing Merchant entity has to be deleted, the following relative URL should be called: 
    "/AppService/merchant/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following MerchantAppInstallation columns: 
    - column: App 
    - column: Merchant 
    - column: InstallDate 
    - column: UninstallDate 
    - column: MonthlyRevenueShareUsd 
The table should have the title "MerchantAppInstallations" und the data must be loaded from the server with the following relative URL: 
    "/AppService/merchantappinstallation/merchant/{id}"

5. The MerchantAppInstallationView must contain the following fields: 
    - name: App   type: App 
    - name: InstallDate   type: DATE 
    - name: Merchant   type: Merchant 
    - name: MonthlyRevenueShareUsd   type: STRING 
    - name: UninstallDate   type: DATE 
The data source for the [App] select control should be loaded from the relative URL: 
    "/AppService/app"   (HTTP-GET) 
The data source for the [Merchant] select control should be loaded from the relative URL: 
    "/AppService/merchant"   (HTTP-GET) 
An existing MerchantAppInstallation entity should be loaded from the relative URL: 
    "/AppService/merchantappinstallation/{id}"   (HTTP-GET) 
If a new MerchantAppInstallation entity has been created, the new entity should be posted to the relative URL: 
    "/AppService/merchantappinstallation"   (HTTP-POST) 
If an existing MerchantAppInstallation entity has been updated, the modified entity should be sent to the relative URL: 
    "/AppService/merchantappinstallation/{id}"   (HTTP-PUT) 
If an existing MerchantAppInstallation entity has to be deleted, the following relative URL should be called: 
    "/AppService/merchantappinstallation/{id}"   (HTTP-DELETE)