Overview
My API
System Designs
Dienstleistungen
Kontakt
Energieausgleich
Ansprechpartner
Impressum
Prompt for the
GreenkeeperApp
Please create a React-JS application for the GreenkeeperModule. The application has to offer the following views for the user interface: 1. AbschlagView 2. GreenkeeperView 3. GreenkeeperGolfplatzView 4. RoughView 5. UmweltbereichView The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 5 views are defined below. 1. The AbschlagView must contain the following fields: - name: Farbe type: STRING - name: Geschlecht type: STRING - name: LaengeMeter type: LONG - name: Loch type: Loch - name: Name type: STRING The data source for the [Loch] select control should be loaded from the relative URL: "/LochService/loch" (HTTP-GET) An existing Abschlag entity should be loaded from the relative URL: "/GreenkeeperService/abschlag/{id}" (HTTP-GET) If a new Abschlag entity has been created, the new entity should be posted to the relative URL: "/GreenkeeperService/abschlag" (HTTP-POST) If an existing Abschlag entity has been updated, the modified entity should be sent to the relative URL: "/GreenkeeperService/abschlag/{id}" (HTTP-PUT) If an existing Abschlag entity has to be deleted, the following relative URL should be called: "/GreenkeeperService/abschlag/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Platzbewertung columns: - column: Hinweise - column: Abschlag - column: GueltigAb - column: SlopeWert - column: Bewertungsstelle - column: Golfplatz - column: Geschlecht - column: RatingWert The table should have the title "Platzbewertungs" und the data must be loaded from the server with the following relative URL: "/GolfplatzService/platzbewertung/abschlag/{id}" 2. The GreenkeeperView must contain the following fields: - name: ArbeitgeberClub type: STRING - name: Hinweise type: STRING - name: Vollname type: STRING - name: Zertifizierung type: STRING An existing Greenkeeper entity should be loaded from the relative URL: "/GreenkeeperService/greenkeeper/{id}" (HTTP-GET) If a new Greenkeeper entity has been created, the new entity should be posted to the relative URL: "/GreenkeeperService/greenkeeper" (HTTP-POST) If an existing Greenkeeper entity has been updated, the modified entity should be sent to the relative URL: "/GreenkeeperService/greenkeeper/{id}" (HTTP-PUT) If an existing Greenkeeper entity has to be deleted, the following relative URL should be called: "/GreenkeeperService/greenkeeper/{id}" (HTTP-DELETE) Add a HTML table to the view with the following GreenkeeperGolfplatz columns: - column: VonDatum - column: Greenkeeper - column: Rolle - column: Golfplatz - column: BisDatum The table should have the title "GreenkeeperGolfplatzs" und the data must be loaded from the server with the following relative URL: "/GreenkeeperService/greenkeepergolfplatz/greenkeeper/{id}" 3. The GreenkeeperGolfplatzView must contain the following fields: - name: BisDatum type: DATE - name: Golfplatz type: Golfplatz - name: Greenkeeper type: Greenkeeper - name: Rolle type: STRING - name: VonDatum type: DATE The data source for the [Golfplatz] select control should be loaded from the relative URL: "/GolfplatzService/golfplatz" (HTTP-GET) The data source for the [Greenkeeper] select control should be loaded from the relative URL: "/GreenkeeperService/greenkeeper" (HTTP-GET) An existing GreenkeeperGolfplatz entity should be loaded from the relative URL: "/GreenkeeperService/greenkeepergolfplatz/{id}" (HTTP-GET) If a new GreenkeeperGolfplatz entity has been created, the new entity should be posted to the relative URL: "/GreenkeeperService/greenkeepergolfplatz" (HTTP-POST) If an existing GreenkeeperGolfplatz entity has been updated, the modified entity should be sent to the relative URL: "/GreenkeeperService/greenkeepergolfplatz/{id}" (HTTP-PUT) If an existing GreenkeeperGolfplatz entity has to be deleted, the following relative URL should be called: "/GreenkeeperService/greenkeepergolfplatz/{id}" (HTTP-DELETE) 4. The RoughView must contain the following fields: - name: Beschreibung type: STRING - name: Grasart type: STRING - name: Loch type: Loch - name: Pflegegrad type: STRING - name: Typ type: STRING The data source for the [Loch] select control should be loaded from the relative URL: "/LochService/loch" (HTTP-GET) An existing Rough entity should be loaded from the relative URL: "/GreenkeeperService/rough/{id}" (HTTP-GET) If a new Rough entity has been created, the new entity should be posted to the relative URL: "/GreenkeeperService/rough" (HTTP-POST) If an existing Rough entity has been updated, the modified entity should be sent to the relative URL: "/GreenkeeperService/rough/{id}" (HTTP-PUT) If an existing Rough entity has to be deleted, the following relative URL should be called: "/GreenkeeperService/rough/{id}" (HTTP-DELETE) 5. The UmweltbereichView must contain the following fields: - name: Beschreibung type: STRING - name: FlaecheQm type: LONG - name: Golfplatz type: Golfplatz - name: Schutzstatus type: STRING - name: Typ type: STRING The data source for the [Golfplatz] select control should be loaded from the relative URL: "/GolfplatzService/golfplatz" (HTTP-GET) An existing Umweltbereich entity should be loaded from the relative URL: "/GreenkeeperService/umweltbereich/{id}" (HTTP-GET) If a new Umweltbereich entity has been created, the new entity should be posted to the relative URL: "/GreenkeeperService/umweltbereich" (HTTP-POST) If an existing Umweltbereich entity has been updated, the modified entity should be sent to the relative URL: "/GreenkeeperService/umweltbereich/{id}" (HTTP-PUT) If an existing Umweltbereich entity has to be deleted, the following relative URL should be called: "/GreenkeeperService/umweltbereich/{id}" (HTTP-DELETE)
Copy prompt
Overview
My API
System Designs
Dienstleistungen
Kontakt
Energieausgleich
Ansprechpartner
Impressum