Overview
Summary
Contact
Donate
Imprint
Prompt for the
CityApp
Please create a React-JS application for the CityModule. The application has to offer the following views for the user interface: 1. AirportView 2. AirportServiceView 3. CityView 4. PublicTransitIntegrationView 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 AirportView must contain the following fields: - name: City type: City - name: IataCode type: STRING - name: Name type: STRING The data source for the [City] select control should be loaded from the relative URL: "/CityService/city" (HTTP-GET) An existing Airport entity should be loaded from the relative URL: "/CityService/airport/{id}" (HTTP-GET) If a new Airport entity has been created, the new entity should be posted to the relative URL: "/CityService/airport" (HTTP-POST) If an existing Airport entity has been updated, the modified entity should be sent to the relative URL: "/CityService/airport/{id}" (HTTP-PUT) If an existing Airport entity has to be deleted, the following relative URL should be called: "/CityService/airport/{id}" (HTTP-DELETE) Add a HTML table to the view with the following AirportService columns: - column: Airport - column: Status - column: RobotaxiService - column: LaunchDate The table should have the title "AirportServices" und the data must be loaded from the server with the following relative URL: "/CityService/airportservice/airport/{id}" 2. The AirportServiceView must contain the following fields: - name: Airport type: Airport - name: LaunchDate type: DATE - name: RobotaxiService type: RobotaxiService - name: Status type: STRING The data source for the [Airport] select control should be loaded from the relative URL: "/CityService/airport" (HTTP-GET) The data source for the [RobotaxiService] select control should be loaded from the relative URL: "/CompanyService/robotaxiservice" (HTTP-GET) An existing AirportService entity should be loaded from the relative URL: "/CityService/airportservice/{id}" (HTTP-GET) If a new AirportService entity has been created, the new entity should be posted to the relative URL: "/CityService/airportservice" (HTTP-POST) If an existing AirportService entity has been updated, the modified entity should be sent to the relative URL: "/CityService/airportservice/{id}" (HTTP-PUT) If an existing AirportService entity has to be deleted, the following relative URL should be called: "/CityService/airportservice/{id}" (HTTP-DELETE) 3. The CityView must contain the following fields: - name: Name type: STRING - name: StateProvince type: StateProvince The data source for the [StateProvince] select control should be loaded from the relative URL: "/CountryService/stateprovince" (HTTP-GET) An existing City entity should be loaded from the relative URL: "/CityService/city/{id}" (HTTP-GET) If a new City entity has been created, the new entity should be posted to the relative URL: "/CityService/city" (HTTP-POST) If an existing City entity has been updated, the modified entity should be sent to the relative URL: "/CityService/city/{id}" (HTTP-PUT) If an existing City entity has to be deleted, the following relative URL should be called: "/CityService/city/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Airport columns: - column: IataCode - column: City - column: Name The table should have the title "Airports" und the data must be loaded from the server with the following relative URL: "/CityService/airport/city/{id}" Add a HTML table to the view with the following ServiceArea columns: - column: Status - column: LaunchDate - column: Notes - column: StateProvince - column: City - column: IsAirport - column: MetroAreaName - column: Country The table should have the title "ServiceAreas" und the data must be loaded from the server with the following relative URL: "/CountryService/servicearea/city/{id}" Add a HTML table to the view with the following ServiceExpansionPlan columns: - column: Status - column: TargetCountry - column: TargetYear - column: TargetCity - column: Notes - column: Program The table should have the title "ServiceExpansionPlans" und the data must be loaded from the server with the following relative URL: "/CountryService/serviceexpansionplan/targetcity/{id}" Add a HTML table to the view with the following PublicTransitIntegration columns: - column: Program - column: Description - column: TransitAgencyName - column: City - column: StartDate The table should have the title "PublicTransitIntegrations" und the data must be loaded from the server with the following relative URL: "/CityService/publictransitintegration/city/{id}" 4. The PublicTransitIntegrationView must contain the following fields: - name: City type: City - name: Description type: STRING - name: Program type: Program - name: StartDate type: DATE - name: TransitAgencyName type: STRING The data source for the [Program] select control should be loaded from the relative URL: "/ProgramService/program" (HTTP-GET) The data source for the [City] select control should be loaded from the relative URL: "/CityService/city" (HTTP-GET) An existing PublicTransitIntegration entity should be loaded from the relative URL: "/CityService/publictransitintegration/{id}" (HTTP-GET) If a new PublicTransitIntegration entity has been created, the new entity should be posted to the relative URL: "/CityService/publictransitintegration" (HTTP-POST) If an existing PublicTransitIntegration entity has been updated, the modified entity should be sent to the relative URL: "/CityService/publictransitintegration/{id}" (HTTP-PUT) If an existing PublicTransitIntegration entity has to be deleted, the following relative URL should be called: "/CityService/publictransitintegration/{id}" (HTTP-DELETE)
Copy prompt
Overview
Summary
Contact
Donate
Imprint