Overview
Summary
Contact
Donate
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. AirportView 2. AirportTransferProductView 3. FlightView 4. FlightBookingSegmentView 5. FlightCarrierView 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 AirportView must contain the following fields: - name: Code type: STRING - name: Latitude type: STRING - name: LocationCity type: LocationCity - name: Longitude type: STRING - name: Name type: STRING The data source for the [LocationCity] select control should be loaded from the relative URL: "/LocationCityService/locationcity" (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 Flight columns: - column: DurationMinutes - column: OriginAirport - column: FlightCarrier - column: DepartureTime - column: FlightNumber - column: ArrivalTime - column: DestinationAirport The table should have the title "Flights" und the data must be loaded from the server with the following relative URL: "/AirportService/flight/destinationairport/{id}" Add a HTML table to the view with the following Flight columns: - column: DurationMinutes - column: OriginAirport - column: FlightCarrier - column: DepartureTime - column: FlightNumber - column: ArrivalTime - column: DestinationAirport The table should have the title "Flights" und the data must be loaded from the server with the following relative URL: "/AirportService/flight/originairport/{id}" Add a HTML table to the view with the following AirportTransferProduct columns: - column: Description - column: DestinationCity - column: MaxPassengers - column: VehicleType - column: Name - column: OriginAirport - column: OriginCity - column: DestinationAirport - column: AirportTransferProvider The table should have the title "AirportTransferProducts" und the data must be loaded from the server with the following relative URL: "/AirportService/airporttransferproduct/originairport/{id}" Add a HTML table to the view with the following AirportTransferProduct columns: - column: Description - column: DestinationCity - column: MaxPassengers - column: VehicleType - column: Name - column: OriginAirport - column: OriginCity - column: DestinationAirport - column: AirportTransferProvider The table should have the title "AirportTransferProducts" und the data must be loaded from the server with the following relative URL: "/AirportService/airporttransferproduct/destinationairport/{id}" 2. The AirportTransferProductView must contain the following fields: - name: AirportTransferProvider type: AirportTransferProvider - name: Description type: STRING - name: DestinationAirport type: Airport - name: DestinationCity type: LocationCity - name: MaxPassengers type: INT - name: Name type: STRING - name: OriginAirport type: Airport - name: OriginCity type: LocationCity - name: VehicleType type: STRING The data source for the [OriginAirport] select control should be loaded from the relative URL: "/AirportService/airport" (HTTP-GET) The data source for the [AirportTransferProvider] select control should be loaded from the relative URL: "/PartnerAccountService/airporttransferprovider" (HTTP-GET) The data source for the [DestinationCity] select control should be loaded from the relative URL: "/LocationCityService/locationcity" (HTTP-GET) The data source for the [OriginCity] select control should be loaded from the relative URL: "/LocationCityService/locationcity" (HTTP-GET) The data source for the [DestinationAirport] select control should be loaded from the relative URL: "/AirportService/airport" (HTTP-GET) An existing AirportTransferProduct entity should be loaded from the relative URL: "/AirportService/airporttransferproduct/{id}" (HTTP-GET) If a new AirportTransferProduct entity has been created, the new entity should be posted to the relative URL: "/AirportService/airporttransferproduct" (HTTP-POST) If an existing AirportTransferProduct entity has been updated, the modified entity should be sent to the relative URL: "/AirportService/airporttransferproduct/{id}" (HTTP-PUT) If an existing AirportTransferProduct entity has to be deleted, the following relative URL should be called: "/AirportService/airporttransferproduct/{id}" (HTTP-DELETE) Add a HTML table to the view with the following AirportTransferBooking columns: - column: PickupAddress - column: Booking - column: PickupDateTime - column: Passengers - column: DropoffAddress - column: AirportTransferProduct - column: TotalAmount - column: Currency The table should have the title "AirportTransferBookings" und the data must be loaded from the server with the following relative URL: "/BookingService/airporttransferbooking/airporttransferproduct/{id}" 3. The FlightView must contain the following fields: - name: ArrivalTime type: DATE - name: DepartureTime type: DATE - name: DestinationAirport type: Airport - name: DurationMinutes type: INT - name: FlightCarrier type: FlightCarrier - name: FlightNumber type: STRING - name: OriginAirport type: Airport The data source for the [FlightCarrier] select control should be loaded from the relative URL: "/AirportService/flightcarrier" (HTTP-GET) The data source for the [OriginAirport] select control should be loaded from the relative URL: "/AirportService/airport" (HTTP-GET) The data source for the [DestinationAirport] select control should be loaded from the relative URL: "/AirportService/airport" (HTTP-GET) An existing Flight entity should be loaded from the relative URL: "/AirportService/flight/{id}" (HTTP-GET) If a new Flight entity has been created, the new entity should be posted to the relative URL: "/AirportService/flight" (HTTP-POST) If an existing Flight entity has been updated, the modified entity should be sent to the relative URL: "/AirportService/flight/{id}" (HTTP-PUT) If an existing Flight entity has to be deleted, the following relative URL should be called: "/AirportService/flight/{id}" (HTTP-DELETE) Add a HTML table to the view with the following FlightBookingSegment columns: - column: Status - column: Flight - column: FlightBooking - column: Seat - column: SegmentNumber The table should have the title "FlightBookingSegments" und the data must be loaded from the server with the following relative URL: "/AirportService/flightbookingsegment/flight/{id}" 4. The FlightBookingSegmentView must contain the following fields: - name: Flight type: Flight - name: FlightBooking type: FlightBooking - name: Seat type: STRING - name: SegmentNumber type: INT - name: Status type: STRING The data source for the [FlightBooking] select control should be loaded from the relative URL: "/CurrencyService/flightbooking" (HTTP-GET) The data source for the [Flight] select control should be loaded from the relative URL: "/AirportService/flight" (HTTP-GET) An existing FlightBookingSegment entity should be loaded from the relative URL: "/AirportService/flightbookingsegment/{id}" (HTTP-GET) If a new FlightBookingSegment entity has been created, the new entity should be posted to the relative URL: "/AirportService/flightbookingsegment" (HTTP-POST) If an existing FlightBookingSegment entity has been updated, the modified entity should be sent to the relative URL: "/AirportService/flightbookingsegment/{id}" (HTTP-PUT) If an existing FlightBookingSegment entity has to be deleted, the following relative URL should be called: "/AirportService/flightbookingsegment/{id}" (HTTP-DELETE) 5. The FlightCarrierView must contain the following fields: - name: Code type: STRING - name: Name type: STRING An existing FlightCarrier entity should be loaded from the relative URL: "/AirportService/flightcarrier/{id}" (HTTP-GET) If a new FlightCarrier entity has been created, the new entity should be posted to the relative URL: "/AirportService/flightcarrier" (HTTP-POST) If an existing FlightCarrier entity has been updated, the modified entity should be sent to the relative URL: "/AirportService/flightcarrier/{id}" (HTTP-PUT) If an existing FlightCarrier entity has to be deleted, the following relative URL should be called: "/AirportService/flightcarrier/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Flight columns: - column: DurationMinutes - column: OriginAirport - column: FlightCarrier - column: DepartureTime - column: FlightNumber - column: ArrivalTime - column: DestinationAirport The table should have the title "Flights" und the data must be loaded from the server with the following relative URL: "/AirportService/flight/flightcarrier/{id}"
Copy prompt
Overview
Summary
Contact
Donate
Imprint