Overview
My API
System Designs
Dienstleistungen
Kontakt
Energieausgleich
Ansprechpartner
Impressum
Prompt for the
SportApp
Please create a React-JS application for the SportModule. The application has to offer the following views for the user interface: 1. EventView 2. SportView 3. TrainingOfferView 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 EventView must contain the following fields: - name: CreatedAt type: DATE - name: Description type: STRING - name: EndDateTime type: DATE - name: LocationText type: STRING - name: MaxParticipants type: LONG - name: Name type: STRING - name: PublicVisible type: BOOL - name: RegistrationDeadline type: DATE - name: Sport type: Sport - name: StartDateTime type: DATE - name: Status type: STRING The data source for the [Sport] select control should be loaded from the relative URL: "/SportService/sport" (HTTP-GET) An existing Event entity should be loaded from the relative URL: "/SportService/event/{id}" (HTTP-GET) If a new Event entity has been created, the new entity should be posted to the relative URL: "/SportService/event" (HTTP-POST) If an existing Event entity has been updated, the modified entity should be sent to the relative URL: "/SportService/event/{id}" (HTTP-PUT) If an existing Event entity has to be deleted, the following relative URL should be called: "/SportService/event/{id}" (HTTP-DELETE) Add a HTML table to the view with the following EventRegistration columns: - column: Status - column: Customer - column: RegisteredAt - column: TeamName - column: Comment - column: Event The table should have the title "EventRegistrations" und the data must be loaded from the server with the following relative URL: "/CustomerService/eventregistration/event/{id}" 2. The SportView must contain the following fields: - name: CreatedAt type: DATE - name: Description type: STRING - name: IsActive type: BOOL - name: Name type: STRING An existing Sport entity should be loaded from the relative URL: "/SportService/sport/{id}" (HTTP-GET) If a new Sport entity has been created, the new entity should be posted to the relative URL: "/SportService/sport" (HTTP-POST) If an existing Sport entity has been updated, the modified entity should be sent to the relative URL: "/SportService/sport/{id}" (HTTP-PUT) If an existing Sport entity has to be deleted, the following relative URL should be called: "/SportService/sport/{id}" (HTTP-DELETE) Add a HTML table to the view with the following PriceItem columns: - column: TimeTo - column: Sport - column: PricePerHour - column: BookingType - column: CreatedAt - column: MembershipType - column: DayOfWeek - column: PriceList - column: TimeFrom The table should have the title "PriceItems" und the data must be loaded from the server with the following relative URL: "/PriceListService/priceitem/sport/{id}" Add a HTML table to the view with the following Event columns: - column: PublicVisible - column: RegistrationDeadline - column: StartDateTime - column: Name - column: LocationText - column: Sport - column: CreatedAt - column: Status - column: Description - column: EndDateTime - column: MaxParticipants The table should have the title "Events" und the data must be loaded from the server with the following relative URL: "/SportService/event/sport/{id}" Add a HTML table to the view with the following Booking columns: - column: CreatedAt - column: EndDateTime - column: Customer - column: BookingType - column: Source - column: Sport - column: Court - column: Status - column: Comment - column: StartDateTime The table should have the title "Bookings" und the data must be loaded from the server with the following relative URL: "/CustomerService/booking/sport/{id}" Add a HTML table to the view with the following TrainingOffer columns: - column: DefaultPrice - column: GroupSizeMin - column: Name - column: Sport - column: DurationMinutes - column: GroupSizeMax - column: Level - column: IsActive - column: CreatedAt - column: Description The table should have the title "TrainingOffers" und the data must be loaded from the server with the following relative URL: "/SportService/trainingoffer/sport/{id}" Add a HTML table to the view with the following CourtSport columns: - column: IsPrimary - column: Court - column: Sport The table should have the title "CourtSports" und the data must be loaded from the server with the following relative URL: "/CourtService/courtsport/sport/{id}" 3. The TrainingOfferView must contain the following fields: - name: CreatedAt type: DATE - name: DefaultPrice type: STRING - name: Description type: STRING - name: DurationMinutes type: LONG - name: GroupSizeMax type: LONG - name: GroupSizeMin type: LONG - name: IsActive type: BOOL - name: Level type: STRING - name: Name type: STRING - name: Sport type: Sport The data source for the [Sport] select control should be loaded from the relative URL: "/SportService/sport" (HTTP-GET) An existing TrainingOffer entity should be loaded from the relative URL: "/SportService/trainingoffer/{id}" (HTTP-GET) If a new TrainingOffer entity has been created, the new entity should be posted to the relative URL: "/SportService/trainingoffer" (HTTP-POST) If an existing TrainingOffer entity has been updated, the modified entity should be sent to the relative URL: "/SportService/trainingoffer/{id}" (HTTP-PUT) If an existing TrainingOffer entity has to be deleted, the following relative URL should be called: "/SportService/trainingoffer/{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/trainingoffer/{id}"
Copy prompt
Overview
My API
System Designs
Dienstleistungen
Kontakt
Energieausgleich
Ansprechpartner
Impressum