Prompt for the AmenityKategorieApp

Please create a React-JS application for the AmenityKategorieModule. The application  has to offer the following views for the user interface: 
    1. AmenityView 
    2. AmenityKategorieView 
    3. BetreiberView 
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: AmenityKategorie   type: AmenityKategorie 
    - name: Beschreibung   type: STRING 
    - name: Code   type: STRING 
    - name: Name   type: STRING 
The data source for the [AmenityKategorie] select control should be loaded from the relative URL: 
    "/AmenityKategorieService/amenitykategorie"   (HTTP-GET) 
An existing Amenity entity should be loaded from the relative URL: 
    "/AmenityKategorieService/amenity/{id}"   (HTTP-GET) 
If a new Amenity entity has been created, the new entity should be posted to the relative URL: 
    "/AmenityKategorieService/amenity"   (HTTP-POST) 
If an existing Amenity entity has been updated, the modified entity should be sent to the relative URL: 
    "/AmenityKategorieService/amenity/{id}"   (HTTP-PUT) 
If an existing Amenity entity has to be deleted, the following relative URL should be called: 
    "/AmenityKategorieService/amenity/{id}"   (HTTP-DELETE)

2. The AmenityKategorieView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Code   type: STRING 
    - name: Name   type: STRING 
An existing AmenityKategorie entity should be loaded from the relative URL: 
    "/AmenityKategorieService/amenitykategorie/{id}"   (HTTP-GET) 
If a new AmenityKategorie entity has been created, the new entity should be posted to the relative URL: 
    "/AmenityKategorieService/amenitykategorie"   (HTTP-POST) 
If an existing AmenityKategorie entity has been updated, the modified entity should be sent to the relative URL: 
    "/AmenityKategorieService/amenitykategorie/{id}"   (HTTP-PUT) 
If an existing AmenityKategorie entity has to be deleted, the following relative URL should be called: 
    "/AmenityKategorieService/amenitykategorie/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Amenity columns: 
    - column: Name 
    - column: AmenityKategorie 
    - column: Code 
    - column: Beschreibung 
The table should have the title "Amenitys" und the data must be loaded from the server with the following relative URL: 
    "/AmenityKategorieService/amenity/amenitykategorie/{id}"

3. The BetreiberView must contain the following fields: 
    - name: Adresse1   type: STRING 
    - name: Adresse2   type: STRING 
    - name: Email   type: STRING 
    - name: Land   type: STRING 
    - name: Name   type: STRING 
    - name: Ort   type: STRING 
    - name: Postleitzahl   type: STRING 
    - name: Rechtsform   type: STRING 
    - name: Steuernummer   type: STRING 
    - name: Telefon   type: STRING 
    - name: WebsiteUrl   type: STRING 
An existing Betreiber entity should be loaded from the relative URL: 
    "/AmenityKategorieService/betreiber/{id}"   (HTTP-GET) 
If a new Betreiber entity has been created, the new entity should be posted to the relative URL: 
    "/AmenityKategorieService/betreiber"   (HTTP-POST) 
If an existing Betreiber entity has been updated, the modified entity should be sent to the relative URL: 
    "/AmenityKategorieService/betreiber/{id}"   (HTTP-PUT) 
If an existing Betreiber entity has to be deleted, the following relative URL should be called: 
    "/AmenityKategorieService/betreiber/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Campingplatz columns: 
    - column: HatHallenbad 
    - column: AnzahlDauerstellplaetze 
    - column: Standort 
    - column: IstFkkPlatz 
    - column: Telefon 
    - column: HatBoule 
    - column: AnzahlStellplaetze 
    - column: HatTrimmDichPfad 
    - column: Email 
    - column: Eroeffnungsdatum 
    - column: NurMikroCamping 
    - column: Name 
    - column: HatSchwimmbad 
    - column: WebsiteUrl 
    - column: HatShop 
    - column: Betreiber 
    - column: HatFitnessbereich 
    - column: Beschreibung 
    - column: Platztyp 
    - column: GanzjaehrigGeoeffnet 
    - column: HatWasserspielbereich 
    - column: Schliessungsdatum 
    - column: AnzahlTouristenplaetze 
    - column: IstUrbanCamping 
    - column: HatSpielplatz 
    - column: HatSwingolf 
    - column: ErlaubtWildcampingAehnlich 
    - column: HatMinigolf 
    - column: HatAnimationsprogramm 
    - column: HatRestaurant 
The table should have the title "Campingplatzs" und the data must be loaded from the server with the following relative URL: 
    "/CampingplatzService/campingplatz/betreiber/{id}"