Prompt for the TraegerTypApp

Please create a React-JS application for the TraegerTypModule. The application  has to offer the following views for the user interface: 
    1. KindergartenTraegerView 
    2. TraegerView 
    3. TraegerTypView 
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 KindergartenTraegerView must contain the following fields: 
    - name: BisDatum   type: DATE 
    - name: Kindergarten   type: Kindergarten 
    - name: Traeger   type: Traeger 
    - name: VonDatum   type: DATE 
The data source for the [Traeger] select control should be loaded from the relative URL: 
    "/TraegerTypService/traeger"   (HTTP-GET) 
The data source for the [Kindergarten] select control should be loaded from the relative URL: 
    "/KindergartenService/kindergarten"   (HTTP-GET) 
An existing KindergartenTraeger entity should be loaded from the relative URL: 
    "/TraegerTypService/kindergartentraeger/{id}"   (HTTP-GET) 
If a new KindergartenTraeger entity has been created, the new entity should be posted to the relative URL: 
    "/TraegerTypService/kindergartentraeger"   (HTTP-POST) 
If an existing KindergartenTraeger entity has been updated, the modified entity should be sent to the relative URL: 
    "/TraegerTypService/kindergartentraeger/{id}"   (HTTP-PUT) 
If an existing KindergartenTraeger entity has to be deleted, the following relative URL should be called: 
    "/TraegerTypService/kindergartentraeger/{id}"   (HTTP-DELETE)

2. The TraegerView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Name   type: STRING 
    - name: ReligioeseZugehoerigkeit   type: STRING 
    - name: TraegerTyp   type: TraegerTyp 
The data source for the [TraegerTyp] select control should be loaded from the relative URL: 
    "/TraegerTypService/traegertyp"   (HTTP-GET) 
An existing Traeger entity should be loaded from the relative URL: 
    "/TraegerTypService/traeger/{id}"   (HTTP-GET) 
If a new Traeger entity has been created, the new entity should be posted to the relative URL: 
    "/TraegerTypService/traeger"   (HTTP-POST) 
If an existing Traeger entity has been updated, the modified entity should be sent to the relative URL: 
    "/TraegerTypService/traeger/{id}"   (HTTP-PUT) 
If an existing Traeger entity has to be deleted, the following relative URL should be called: 
    "/TraegerTypService/traeger/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following KindergartenTraeger columns: 
    - column: Traeger 
    - column: BisDatum 
    - column: Kindergarten 
    - column: VonDatum 
The table should have the title "KindergartenTraegers" und the data must be loaded from the server with the following relative URL: 
    "/TraegerTypService/kindergartentraeger/traeger/{id}"

3. The TraegerTypView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Name   type: STRING 
An existing TraegerTyp entity should be loaded from the relative URL: 
    "/TraegerTypService/traegertyp/{id}"   (HTTP-GET) 
If a new TraegerTyp entity has been created, the new entity should be posted to the relative URL: 
    "/TraegerTypService/traegertyp"   (HTTP-POST) 
If an existing TraegerTyp entity has been updated, the modified entity should be sent to the relative URL: 
    "/TraegerTypService/traegertyp/{id}"   (HTTP-PUT) 
If an existing TraegerTyp entity has to be deleted, the following relative URL should be called: 
    "/TraegerTypService/traegertyp/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Traeger columns: 
    - column: Name 
    - column: TraegerTyp 
    - column: Beschreibung 
    - column: ReligioeseZugehoerigkeit 
The table should have the title "Traegers" und the data must be loaded from the server with the following relative URL: 
    "/TraegerTypService/traeger/traegertyp/{id}"