Prompt for the AmenityApp

Please create a React-JS application for the AmenityModule. The application  has to offer the following views for the user interface: 
    1. AmenityView 
    2. ListingAmenityView 
    3. UserDataConsentView 
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 AmenityView must contain the following fields: 
    - name: Category   type: STRING 
    - name: Name   type: STRING 
An existing Amenity entity should be loaded from the relative URL: 
    "/AmenityService/amenity/{id}"   (HTTP-GET) 
If a new Amenity entity has been created, the new entity should be posted to the relative URL: 
    "/AmenityService/amenity"   (HTTP-POST) 
If an existing Amenity entity has been updated, the modified entity should be sent to the relative URL: 
    "/AmenityService/amenity/{id}"   (HTTP-PUT) 
If an existing Amenity entity has to be deleted, the following relative URL should be called: 
    "/AmenityService/amenity/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following ListingAmenity columns: 
    - column: Listing 
    - column: Amenity 
The table should have the title "ListingAmenitys" und the data must be loaded from the server with the following relative URL: 
    "/AmenityService/listingamenity/amenity/{id}"

2. The ListingAmenityView must contain the following fields: 
    - name: Amenity   type: Amenity 
    - name: Listing   type: Listing 
The data source for the [Amenity] select control should be loaded from the relative URL: 
    "/AmenityService/amenity"   (HTTP-GET) 
The data source for the [Listing] select control should be loaded from the relative URL: 
    "/ListingService/listing"   (HTTP-GET) 
An existing ListingAmenity entity should be loaded from the relative URL: 
    "/AmenityService/listingamenity/{id}"   (HTTP-GET) 
If a new ListingAmenity entity has been created, the new entity should be posted to the relative URL: 
    "/AmenityService/listingamenity"   (HTTP-POST) 
If an existing ListingAmenity entity has been updated, the modified entity should be sent to the relative URL: 
    "/AmenityService/listingamenity/{id}"   (HTTP-PUT) 
If an existing ListingAmenity entity has to be deleted, the following relative URL should be called: 
    "/AmenityService/listingamenity/{id}"   (HTTP-DELETE)

3. The UserDataConsentView must contain the following fields: 
    - name: ConsentType   type: STRING 
    - name: Description   type: STRING 
    - name: GrantedAt   type: DATE 
    - name: PlatformUser   type: PlatformUser 
    - name: RevokedAt   type: DATE 
The data source for the [PlatformUser] select control should be loaded from the relative URL: 
    "/PlatformUserService/platformuser"   (HTTP-GET) 
An existing UserDataConsent entity should be loaded from the relative URL: 
    "/AmenityService/userdataconsent/{id}"   (HTTP-GET) 
If a new UserDataConsent entity has been created, the new entity should be posted to the relative URL: 
    "/AmenityService/userdataconsent"   (HTTP-POST) 
If an existing UserDataConsent entity has been updated, the modified entity should be sent to the relative URL: 
    "/AmenityService/userdataconsent/{id}"   (HTTP-PUT) 
If an existing UserDataConsent entity has to be deleted, the following relative URL should be called: 
    "/AmenityService/userdataconsent/{id}"   (HTTP-DELETE)