Prompt for the GastronomyUnitApp

Please create a React-JS application for the GastronomyUnitModule. The application  has to offer the following views for the user interface: 
    1. GastronomyUnitView 
    2. MenuCategoryView 
    3. MenuItemView 
    4. MenuItemAllergenView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below.

1. The GastronomyUnitView must contain the following fields: 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
    - name: OpeningHours   type: STRING 
    - name: Type   type: STRING 
    - name: VenueArea   type: VenueArea 
The data source for the [VenueArea] select control should be loaded from the relative URL: 
    "/VenueAreaService/venuearea"   (HTTP-GET) 
An existing GastronomyUnit entity should be loaded from the relative URL: 
    "/GastronomyUnitService/gastronomyunit/{id}"   (HTTP-GET) 
If a new GastronomyUnit entity has been created, the new entity should be posted to the relative URL: 
    "/GastronomyUnitService/gastronomyunit"   (HTTP-POST) 
If an existing GastronomyUnit entity has been updated, the modified entity should be sent to the relative URL: 
    "/GastronomyUnitService/gastronomyunit/{id}"   (HTTP-PUT) 
If an existing GastronomyUnit entity has to be deleted, the following relative URL should be called: 
    "/GastronomyUnitService/gastronomyunit/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following MenuItem columns: 
    - column: Description 
    - column: MenuCategory 
    - column: GastronomyUnit 
    - column: IsVegan 
    - column: IsVegetarian 
    - column: IsAlcoholic 
    - column: Price 
    - column: Name 
The table should have the title "MenuItems" und the data must be loaded from the server with the following relative URL: 
    "/GastronomyUnitService/menuitem/gastronomyunit/{id}"

2. The MenuCategoryView must contain the following fields: 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
An existing MenuCategory entity should be loaded from the relative URL: 
    "/GastronomyUnitService/menucategory/{id}"   (HTTP-GET) 
If a new MenuCategory entity has been created, the new entity should be posted to the relative URL: 
    "/GastronomyUnitService/menucategory"   (HTTP-POST) 
If an existing MenuCategory entity has been updated, the modified entity should be sent to the relative URL: 
    "/GastronomyUnitService/menucategory/{id}"   (HTTP-PUT) 
If an existing MenuCategory entity has to be deleted, the following relative URL should be called: 
    "/GastronomyUnitService/menucategory/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following MenuItem columns: 
    - column: Description 
    - column: MenuCategory 
    - column: GastronomyUnit 
    - column: IsVegan 
    - column: IsVegetarian 
    - column: IsAlcoholic 
    - column: Price 
    - column: Name 
The table should have the title "MenuItems" und the data must be loaded from the server with the following relative URL: 
    "/GastronomyUnitService/menuitem/menucategory/{id}"

3. The MenuItemView must contain the following fields: 
    - name: Description   type: STRING 
    - name: GastronomyUnit   type: GastronomyUnit 
    - name: IsAlcoholic   type: BOOL 
    - name: IsVegan   type: BOOL 
    - name: IsVegetarian   type: BOOL 
    - name: MenuCategory   type: MenuCategory 
    - name: Name   type: STRING 
    - name: Price   type: STRING 
The data source for the [GastronomyUnit] select control should be loaded from the relative URL: 
    "/GastronomyUnitService/gastronomyunit"   (HTTP-GET) 
The data source for the [MenuCategory] select control should be loaded from the relative URL: 
    "/GastronomyUnitService/menucategory"   (HTTP-GET) 
An existing MenuItem entity should be loaded from the relative URL: 
    "/GastronomyUnitService/menuitem/{id}"   (HTTP-GET) 
If a new MenuItem entity has been created, the new entity should be posted to the relative URL: 
    "/GastronomyUnitService/menuitem"   (HTTP-POST) 
If an existing MenuItem entity has been updated, the modified entity should be sent to the relative URL: 
    "/GastronomyUnitService/menuitem/{id}"   (HTTP-PUT) 
If an existing MenuItem entity has to be deleted, the following relative URL should be called: 
    "/GastronomyUnitService/menuitem/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following MenuItemAllergen columns: 
    - column: AllergenCode 
    - column: MenuItem 
    - column: Description 
The table should have the title "MenuItemAllergens" und the data must be loaded from the server with the following relative URL: 
    "/GastronomyUnitService/menuitemallergen/menuitem/{id}"

4. The MenuItemAllergenView must contain the following fields: 
    - name: AllergenCode   type: STRING 
    - name: Description   type: STRING 
    - name: MenuItem   type: MenuItem 
The data source for the [MenuItem] select control should be loaded from the relative URL: 
    "/GastronomyUnitService/menuitem"   (HTTP-GET) 
An existing MenuItemAllergen entity should be loaded from the relative URL: 
    "/GastronomyUnitService/menuitemallergen/{id}"   (HTTP-GET) 
If a new MenuItemAllergen entity has been created, the new entity should be posted to the relative URL: 
    "/GastronomyUnitService/menuitemallergen"   (HTTP-POST) 
If an existing MenuItemAllergen entity has been updated, the modified entity should be sent to the relative URL: 
    "/GastronomyUnitService/menuitemallergen/{id}"   (HTTP-PUT) 
If an existing MenuItemAllergen entity has to be deleted, the following relative URL should be called: 
    "/GastronomyUnitService/menuitemallergen/{id}"   (HTTP-DELETE)