Overview
Summary
Contact
Donate
Imprint
Prompt for the
LocationCityApp
Please create a React-JS application for the LocationCityModule. The application has to offer the following views for the user interface: 1. FlightPassengerView 2. LocationCityView 3. LocationCountryView 4. LocationRegionView 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 FlightPassengerView must contain the following fields: - name: DateOfBirth type: DATE - name: DocumentNumber type: STRING - name: FlightBooking type: FlightBooking - name: FullName type: STRING - name: NationalityCountry type: LocationCountry - name: PassengerType 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 [NationalityCountry] select control should be loaded from the relative URL: "/LocationCityService/locationcountry" (HTTP-GET) An existing FlightPassenger entity should be loaded from the relative URL: "/LocationCityService/flightpassenger/{id}" (HTTP-GET) If a new FlightPassenger entity has been created, the new entity should be posted to the relative URL: "/LocationCityService/flightpassenger" (HTTP-POST) If an existing FlightPassenger entity has been updated, the modified entity should be sent to the relative URL: "/LocationCityService/flightpassenger/{id}" (HTTP-PUT) If an existing FlightPassenger entity has to be deleted, the following relative URL should be called: "/LocationCityService/flightpassenger/{id}" (HTTP-DELETE) 2. The LocationCityView must contain the following fields: - name: Latitude type: STRING - name: LocationCountry type: LocationCountry - name: LocationRegion type: LocationRegion - name: Longitude type: STRING - name: Name type: STRING The data source for the [LocationRegion] select control should be loaded from the relative URL: "/LocationCityService/locationregion" (HTTP-GET) The data source for the [LocationCountry] select control should be loaded from the relative URL: "/LocationCityService/locationcountry" (HTTP-GET) An existing LocationCity entity should be loaded from the relative URL: "/LocationCityService/locationcity/{id}" (HTTP-GET) If a new LocationCity entity has been created, the new entity should be posted to the relative URL: "/LocationCityService/locationcity" (HTTP-POST) If an existing LocationCity entity has been updated, the modified entity should be sent to the relative URL: "/LocationCityService/locationcity/{id}" (HTTP-PUT) If an existing LocationCity entity has to be deleted, the following relative URL should be called: "/LocationCityService/locationcity/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Property columns: - column: Latitude - column: StarRating - column: AddressLine1 - column: LocationCity - column: AddressLine2 - column: PropertyType - column: LocationDistrict - column: IsActive - column: PostalCode - column: CheckInTo - column: LocationCountry - column: CreatedAt - column: CheckOutFrom - column: PartnerAccount - column: Longitude - column: CheckInFrom - column: CheckOutTo - column: Name The table should have the title "Propertys" und the data must be loaded from the server with the following relative URL: "/PropertyService/property/locationcity/{id}" Add a HTML table to the view with the following Airport columns: - column: Code - column: Name - column: Latitude - column: Longitude - column: LocationCity The table should have the title "Airports" und the data must be loaded from the server with the following relative URL: "/AirportService/airport/locationcity/{id}" Add a HTML table to the view with the following LocationDistrict columns: - column: Name - column: LocationCity The table should have the title "LocationDistricts" und the data must be loaded from the server with the following relative URL: "/PropertyService/locationdistrict/locationcity/{id}" Add a HTML table to the view with the following CarRentalLocation columns: - column: Latitude - column: PostalCode - column: Longitude - column: AddressLine2 - column: LocationCity - column: Name - column: PartnerAccount - column: AddressLine1 The table should have the title "CarRentalLocations" und the data must be loaded from the server with the following relative URL: "/CarRentalLocationService/carrentallocation/locationcity/{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/destinationcity/{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/origincity/{id}" Add a HTML table to the view with the following Attraction columns: - column: Description - column: Name - column: Latitude - column: Longitude - column: AddressLine2 - column: LocationCity - column: PartnerAccount - column: AddressLine1 - column: PostalCode The table should have the title "Attractions" und the data must be loaded from the server with the following relative URL: "/PartnerAccountService/attraction/locationcity/{id}" 3. The LocationCountryView must contain the following fields: - name: Code type: STRING - name: Name type: STRING An existing LocationCountry entity should be loaded from the relative URL: "/LocationCityService/locationcountry/{id}" (HTTP-GET) If a new LocationCountry entity has been created, the new entity should be posted to the relative URL: "/LocationCityService/locationcountry" (HTTP-POST) If an existing LocationCountry entity has been updated, the modified entity should be sent to the relative URL: "/LocationCityService/locationcountry/{id}" (HTTP-PUT) If an existing LocationCountry entity has to be deleted, the following relative URL should be called: "/LocationCityService/locationcountry/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Property columns: - column: Latitude - column: StarRating - column: AddressLine1 - column: LocationCity - column: AddressLine2 - column: PropertyType - column: LocationDistrict - column: IsActive - column: PostalCode - column: CheckInTo - column: LocationCountry - column: CreatedAt - column: CheckOutFrom - column: PartnerAccount - column: Longitude - column: CheckInFrom - column: CheckOutTo - column: Name The table should have the title "Propertys" und the data must be loaded from the server with the following relative URL: "/PropertyService/property/locationcountry/{id}" Add a HTML table to the view with the following LocationCity columns: - column: Name - column: LocationRegion - column: LocationCountry - column: Latitude - column: Longitude The table should have the title "LocationCitys" und the data must be loaded from the server with the following relative URL: "/LocationCityService/locationcity/locationcountry/{id}" Add a HTML table to the view with the following FlightPassenger columns: - column: NationalityCountry - column: PassengerType - column: DocumentNumber - column: FullName - column: FlightBooking - column: DateOfBirth The table should have the title "FlightPassengers" und the data must be loaded from the server with the following relative URL: "/LocationCityService/flightpassenger/nationalitycountry/{id}" Add a HTML table to the view with the following LocationRegion columns: - column: Name - column: LocationCountry The table should have the title "LocationRegions" und the data must be loaded from the server with the following relative URL: "/LocationCityService/locationregion/locationcountry/{id}" 4. The LocationRegionView must contain the following fields: - name: LocationCountry type: LocationCountry - name: Name type: STRING The data source for the [LocationCountry] select control should be loaded from the relative URL: "/LocationCityService/locationcountry" (HTTP-GET) An existing LocationRegion entity should be loaded from the relative URL: "/LocationCityService/locationregion/{id}" (HTTP-GET) If a new LocationRegion entity has been created, the new entity should be posted to the relative URL: "/LocationCityService/locationregion" (HTTP-POST) If an existing LocationRegion entity has been updated, the modified entity should be sent to the relative URL: "/LocationCityService/locationregion/{id}" (HTTP-PUT) If an existing LocationRegion entity has to be deleted, the following relative URL should be called: "/LocationCityService/locationregion/{id}" (HTTP-DELETE) Add a HTML table to the view with the following LocationCity columns: - column: Name - column: LocationRegion - column: LocationCountry - column: Latitude - column: Longitude The table should have the title "LocationCitys" und the data must be loaded from the server with the following relative URL: "/LocationCityService/locationcity/locationregion/{id}"
Copy prompt
Overview
Summary
Contact
Donate
Imprint