Prompt for the GeraeteTypApp

Please create a React-JS application for the GeraeteTypModule. The application  has to offer the following views for the user interface: 
    1. GeraetView 
    2. GeraeteTypView 
    3. GeraeteWartungView 
    4. SportVereinView 
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 GeraetView must contain the following fields: 
    - name: FitnessStudio   type: FitnessStudio 
    - name: GeraeteTyp   type: GeraeteTyp 
    - name: IstAktiv   type: BOOL 
    - name: KaufDatum   type: DATE 
    - name: SerienNummer   type: STRING 
    - name: StandortBeschreibung   type: STRING 
The data source for the [FitnessStudio] select control should be loaded from the relative URL: 
    "/FitnessStudioService/fitnessstudio"   (HTTP-GET) 
The data source for the [GeraeteTyp] select control should be loaded from the relative URL: 
    "/GeraeteTypService/geraetetyp"   (HTTP-GET) 
An existing Geraet entity should be loaded from the relative URL: 
    "/GeraeteTypService/geraet/{id}"   (HTTP-GET) 
If a new Geraet entity has been created, the new entity should be posted to the relative URL: 
    "/GeraeteTypService/geraet"   (HTTP-POST) 
If an existing Geraet entity has been updated, the modified entity should be sent to the relative URL: 
    "/GeraeteTypService/geraet/{id}"   (HTTP-PUT) 
If an existing Geraet entity has to be deleted, the following relative URL should be called: 
    "/GeraeteTypService/geraet/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following GeraeteWartung columns: 
    - column: Geraet 
    - column: DurchgefuehrtVon 
    - column: Beschreibung 
    - column: IstGeplant 
    - column: WartungsDatum 
    - column: NaechsteFaelligkeit 
The table should have the title "GeraeteWartungs" und the data must be loaded from the server with the following relative URL: 
    "/GeraeteTypService/geraetewartung/geraet/{id}"

2. The GeraeteTypView must contain the following fields: 
    - name: Hersteller   type: STRING 
    - name: IstCardio   type: BOOL 
    - name: Kategorie   type: STRING 
    - name: Name   type: STRING 
    - name: ZielMuskelGruppe   type: STRING 
An existing GeraeteTyp entity should be loaded from the relative URL: 
    "/GeraeteTypService/geraetetyp/{id}"   (HTTP-GET) 
If a new GeraeteTyp entity has been created, the new entity should be posted to the relative URL: 
    "/GeraeteTypService/geraetetyp"   (HTTP-POST) 
If an existing GeraeteTyp entity has been updated, the modified entity should be sent to the relative URL: 
    "/GeraeteTypService/geraetetyp/{id}"   (HTTP-PUT) 
If an existing GeraeteTyp entity has to be deleted, the following relative URL should be called: 
    "/GeraeteTypService/geraetetyp/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Geraet columns: 
    - column: StandortBeschreibung 
    - column: SerienNummer 
    - column: KaufDatum 
    - column: FitnessStudio 
    - column: GeraeteTyp 
    - column: IstAktiv 
The table should have the title "Geraets" und the data must be loaded from the server with the following relative URL: 
    "/GeraeteTypService/geraet/geraetetyp/{id}"

3. The GeraeteWartungView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: DurchgefuehrtVon   type: STRING 
    - name: Geraet   type: Geraet 
    - name: IstGeplant   type: BOOL 
    - name: NaechsteFaelligkeit   type: DATE 
    - name: WartungsDatum   type: DATE 
The data source for the [Geraet] select control should be loaded from the relative URL: 
    "/GeraeteTypService/geraet"   (HTTP-GET) 
An existing GeraeteWartung entity should be loaded from the relative URL: 
    "/GeraeteTypService/geraetewartung/{id}"   (HTTP-GET) 
If a new GeraeteWartung entity has been created, the new entity should be posted to the relative URL: 
    "/GeraeteTypService/geraetewartung"   (HTTP-POST) 
If an existing GeraeteWartung entity has been updated, the modified entity should be sent to the relative URL: 
    "/GeraeteTypService/geraetewartung/{id}"   (HTTP-PUT) 
If an existing GeraeteWartung entity has to be deleted, the following relative URL should be called: 
    "/GeraeteTypService/geraetewartung/{id}"   (HTTP-DELETE)

4. The SportVereinView must contain the following fields: 
    - name: IstGemeinnuetzig   type: BOOL 
    - name: Land   type: STRING 
    - name: Name   type: STRING 
    - name: Postleitzahl   type: STRING 
    - name: Rechtsform   type: STRING 
    - name: Stadt   type: STRING 
    - name: Strasse   type: STRING 
An existing SportVerein entity should be loaded from the relative URL: 
    "/GeraeteTypService/sportverein/{id}"   (HTTP-GET) 
If a new SportVerein entity has been created, the new entity should be posted to the relative URL: 
    "/GeraeteTypService/sportverein"   (HTTP-POST) 
If an existing SportVerein entity has been updated, the modified entity should be sent to the relative URL: 
    "/GeraeteTypService/sportverein/{id}"   (HTTP-PUT) 
If an existing SportVerein entity has to be deleted, the following relative URL should be called: 
    "/GeraeteTypService/sportverein/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following FitnessStudio columns: 
    - column: GroesseQuadratmeter 
    - column: Strasse 
    - column: FranchiseSystem 
    - column: SportVerein 
    - column: Name 
    - column: FitnessKette 
    - column: Postleitzahl 
    - column: Stadt 
    - column: StudioTyp 
    - column: IstMikrostudio 
    - column: Land 
    - column: Ist24StundenGeoeffnet 
    - column: Oeffnungszeiten 
The table should have the title "FitnessStudios" und the data must be loaded from the server with the following relative URL: 
    "/FitnessStudioService/fitnessstudio/sportverein/{id}"