Overview
My API
System Designs
Dienstleistungen
Kontakt
Energieausgleich
Ansprechpartner
Impressum
Prompt for the
TrainingSessionApp
Please create a React-JS application for the TrainingSessionModule. The application has to offer the following views for the user interface: 1. CoachView 2. TrainingParticipantView 3. TrainingSessionView 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 CoachView must contain the following fields: - name: ActiveSince type: DATE - name: CreatedAt type: DATE - name: Email type: STRING - name: FirstName type: STRING - name: IsActive type: BOOL - name: IsExternal type: BOOL - name: LastName type: STRING - name: Phone type: STRING - name: ShortBio type: STRING An existing Coach entity should be loaded from the relative URL: "/TrainingSessionService/coach/{id}" (HTTP-GET) If a new Coach entity has been created, the new entity should be posted to the relative URL: "/TrainingSessionService/coach" (HTTP-POST) If an existing Coach entity has been updated, the modified entity should be sent to the relative URL: "/TrainingSessionService/coach/{id}" (HTTP-PUT) If an existing Coach entity has to be deleted, the following relative URL should be called: "/TrainingSessionService/coach/{id}" (HTTP-DELETE) Add a HTML table to the view with the following TrainingSession columns: - column: Court - column: EndDateTime - column: Status - column: CreatedAt - column: MaxParticipants - column: StartDateTime - column: TrainingOffer - column: Coach The table should have the title "TrainingSessions" und the data must be loaded from the server with the following relative URL: "/TrainingSessionService/trainingsession/coach/{id}" 2. The TrainingParticipantView must contain the following fields: - name: Customer type: Customer - name: PriceOverride type: STRING - name: RegisteredAt type: DATE - name: Role type: STRING - name: TrainingSession type: TrainingSession The data source for the [Customer] select control should be loaded from the relative URL: "/CustomerService/customer" (HTTP-GET) The data source for the [TrainingSession] select control should be loaded from the relative URL: "/TrainingSessionService/trainingsession" (HTTP-GET) An existing TrainingParticipant entity should be loaded from the relative URL: "/TrainingSessionService/trainingparticipant/{id}" (HTTP-GET) If a new TrainingParticipant entity has been created, the new entity should be posted to the relative URL: "/TrainingSessionService/trainingparticipant" (HTTP-POST) If an existing TrainingParticipant entity has been updated, the modified entity should be sent to the relative URL: "/TrainingSessionService/trainingparticipant/{id}" (HTTP-PUT) If an existing TrainingParticipant entity has to be deleted, the following relative URL should be called: "/TrainingSessionService/trainingparticipant/{id}" (HTTP-DELETE) 3. The TrainingSessionView must contain the following fields: - name: Coach type: Coach - name: Court type: Court - name: CreatedAt type: DATE - name: EndDateTime type: DATE - name: MaxParticipants type: LONG - name: StartDateTime type: DATE - name: Status type: STRING - name: TrainingOffer type: TrainingOffer The data source for the [Coach] select control should be loaded from the relative URL: "/TrainingSessionService/coach" (HTTP-GET) The data source for the [Court] select control should be loaded from the relative URL: "/CourtService/court" (HTTP-GET) The data source for the [TrainingOffer] select control should be loaded from the relative URL: "/SportService/trainingoffer" (HTTP-GET) An existing TrainingSession entity should be loaded from the relative URL: "/TrainingSessionService/trainingsession/{id}" (HTTP-GET) If a new TrainingSession entity has been created, the new entity should be posted to the relative URL: "/TrainingSessionService/trainingsession" (HTTP-POST) If an existing TrainingSession entity has been updated, the modified entity should be sent to the relative URL: "/TrainingSessionService/trainingsession/{id}" (HTTP-PUT) If an existing TrainingSession entity has to be deleted, the following relative URL should be called: "/TrainingSessionService/trainingsession/{id}" (HTTP-DELETE) Add a HTML table to the view with the following TrainingParticipant columns: - column: Role - column: Customer - column: TrainingSession - column: RegisteredAt - column: PriceOverride The table should have the title "TrainingParticipants" und the data must be loaded from the server with the following relative URL: "/TrainingSessionService/trainingparticipant/trainingsession/{id}"
Copy prompt
Overview
My API
System Designs
Dienstleistungen
Kontakt
Energieausgleich
Ansprechpartner
Impressum