Overview
Summary
Services
Contact
Donate
About
Imprint
Prompt for the
AirportApp
Please create a React-JS application for the AirportModule. The application has to offer the following views for the user interface: 1. AirlineHubView 2. AirportView 3. BaggageItemView 4. BookingPassengerView 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 AirlineHubView must contain the following fields: - name: Airline type: Airline - name: Airport type: Airport - name: HubType type: STRING - name: SinceDate type: DATE The data source for the [Airline] select control should be loaded from the relative URL: "/AirlineService/airline" (HTTP-GET) The data source for the [Airport] select control should be loaded from the relative URL: "/AirportService/airport" (HTTP-GET) An existing AirlineHub entity should be loaded from the relative URL: "/AirportService/airlinehub/{id}" (HTTP-GET) If a new AirlineHub entity has been created, the new entity should be posted to the relative URL: "/AirportService/airlinehub" (HTTP-POST) If an existing AirlineHub entity has been updated, the modified entity should be sent to the relative URL: "/AirportService/airlinehub/{id}" (HTTP-PUT) If an existing AirlineHub entity has to be deleted, the following relative URL should be called: "/AirportService/airlinehub/{id}" (HTTP-DELETE) 2. The AirportView must contain the following fields: - name: AirportType type: STRING - name: City type: STRING - name: Country type: Country - name: Elevation type: LONG - name: IataCode type: STRING - name: IcaoCode type: STRING - name: Latitude type: STRING - name: Longitude type: STRING - name: Name type: STRING - name: TimeZone type: STRING The data source for the [Country] select control should be loaded from the relative URL: "/CountryService/country" (HTTP-GET) An existing Airport entity should be loaded from the relative URL: "/AirportService/airport/{id}" (HTTP-GET) If a new Airport entity has been created, the new entity should be posted to the relative URL: "/AirportService/airport" (HTTP-POST) If an existing Airport entity has been updated, the modified entity should be sent to the relative URL: "/AirportService/airport/{id}" (HTTP-PUT) If an existing Airport entity has to be deleted, the following relative URL should be called: "/AirportService/airport/{id}" (HTTP-DELETE) Add a HTML table to the view with the following AirlineHub columns: - column: HubType - column: Airport - column: SinceDate - column: Airline The table should have the title "AirlineHubs" und the data must be loaded from the server with the following relative URL: "/AirportService/airlinehub/airport/{id}" Add a HTML table to the view with the following BaggageItem columns: - column: CheckedInAirport - column: FinalAirport - column: Status - column: TagNumber - column: WeightKg - column: BookingPassenger The table should have the title "BaggageItems" und the data must be loaded from the server with the following relative URL: "/AirportService/baggageitem/finalairport/{id}" Add a HTML table to the view with the following BaggageItem columns: - column: CheckedInAirport - column: FinalAirport - column: Status - column: TagNumber - column: WeightKg - column: BookingPassenger The table should have the title "BaggageItems" und the data must be loaded from the server with the following relative URL: "/AirportService/baggageitem/checkedinairport/{id}" Add a HTML table to the view with the following Route columns: - column: DomesticInternational - column: DestinationAirport - column: Airline - column: ActiveFrom - column: OriginAirport - column: ActiveTo - column: DistanceKm The table should have the title "Routes" und the data must be loaded from the server with the following relative URL: "/FlightNumberService/route/destinationairport/{id}" Add a HTML table to the view with the following Route columns: - column: DomesticInternational - column: DestinationAirport - column: Airline - column: ActiveFrom - column: OriginAirport - column: ActiveTo - column: DistanceKm The table should have the title "Routes" und the data must be loaded from the server with the following relative URL: "/FlightNumberService/route/originairport/{id}" 3. The BaggageItemView must contain the following fields: - name: BookingPassenger type: BookingPassenger - name: CheckedInAirport type: Airport - name: FinalAirport type: Airport - name: Status type: STRING - name: TagNumber type: STRING - name: WeightKg type: STRING The data source for the [CheckedInAirport] select control should be loaded from the relative URL: "/AirportService/airport" (HTTP-GET) The data source for the [FinalAirport] select control should be loaded from the relative URL: "/AirportService/airport" (HTTP-GET) The data source for the [BookingPassenger] select control should be loaded from the relative URL: "/AirportService/bookingpassenger" (HTTP-GET) An existing BaggageItem entity should be loaded from the relative URL: "/AirportService/baggageitem/{id}" (HTTP-GET) If a new BaggageItem entity has been created, the new entity should be posted to the relative URL: "/AirportService/baggageitem" (HTTP-POST) If an existing BaggageItem entity has been updated, the modified entity should be sent to the relative URL: "/AirportService/baggageitem/{id}" (HTTP-PUT) If an existing BaggageItem entity has to be deleted, the following relative URL should be called: "/AirportService/baggageitem/{id}" (HTTP-DELETE) 4. The BookingPassengerView must contain the following fields: - name: Booking type: Booking - name: LoyaltyStatus type: STRING - name: Passenger type: Passenger - name: PassengerType type: STRING The data source for the [Booking] select control should be loaded from the relative URL: "/BookingService/booking" (HTTP-GET) The data source for the [Passenger] select control should be loaded from the relative URL: "/AirlineService/passenger" (HTTP-GET) An existing BookingPassenger entity should be loaded from the relative URL: "/AirportService/bookingpassenger/{id}" (HTTP-GET) If a new BookingPassenger entity has been created, the new entity should be posted to the relative URL: "/AirportService/bookingpassenger" (HTTP-POST) If an existing BookingPassenger entity has been updated, the modified entity should be sent to the relative URL: "/AirportService/bookingpassenger/{id}" (HTTP-PUT) If an existing BookingPassenger entity has to be deleted, the following relative URL should be called: "/AirportService/bookingpassenger/{id}" (HTTP-DELETE) Add a HTML table to the view with the following BaggageItem columns: - column: CheckedInAirport - column: FinalAirport - column: Status - column: TagNumber - column: WeightKg - column: BookingPassenger The table should have the title "BaggageItems" und the data must be loaded from the server with the following relative URL: "/AirportService/baggageitem/bookingpassenger/{id}"
Copy prompt
Overview
Summary
Services
Contact
Donate
About
Imprint