Overview
Summary
Contact
Donate
Imprint
Prompt for the
CarRentalLocationApp
Please create a React-JS application for the CarRentalLocationModule. The application has to offer the following views for the user interface: 1. CarRentalBookingView 2. CarRentalLocationView 3. RoomTypeCategoryView 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 CarRentalBookingView must contain the following fields: - name: Booking type: Booking - name: CarRentalProduct type: CarRentalProduct - name: Currency type: Currency - name: DropoffDateTime type: DATE - name: DropoffLocation type: CarRentalLocation - name: PickupDateTime type: DATE - name: PickupLocation type: CarRentalLocation - name: TotalAmount type: STRING The data source for the [PickupLocation] select control should be loaded from the relative URL: "/CarRentalLocationService/carrentallocation" (HTTP-GET) The data source for the [CarRentalProduct] select control should be loaded from the relative URL: "/CarCategoryService/carrentalproduct" (HTTP-GET) The data source for the [Currency] select control should be loaded from the relative URL: "/CurrencyService/currency" (HTTP-GET) The data source for the [Booking] select control should be loaded from the relative URL: "/BookingService/booking" (HTTP-GET) The data source for the [DropoffLocation] select control should be loaded from the relative URL: "/CarRentalLocationService/carrentallocation" (HTTP-GET) An existing CarRentalBooking entity should be loaded from the relative URL: "/CarRentalLocationService/carrentalbooking/{id}" (HTTP-GET) If a new CarRentalBooking entity has been created, the new entity should be posted to the relative URL: "/CarRentalLocationService/carrentalbooking" (HTTP-POST) If an existing CarRentalBooking entity has been updated, the modified entity should be sent to the relative URL: "/CarRentalLocationService/carrentalbooking/{id}" (HTTP-PUT) If an existing CarRentalBooking entity has to be deleted, the following relative URL should be called: "/CarRentalLocationService/carrentalbooking/{id}" (HTTP-DELETE) 2. The CarRentalLocationView must contain the following fields: - name: AddressLine1 type: STRING - name: AddressLine2 type: STRING - name: Latitude type: STRING - name: LocationCity type: LocationCity - name: Longitude type: STRING - name: Name type: STRING - name: PartnerAccount type: PartnerAccount - name: PostalCode type: STRING The data source for the [PartnerAccount] select control should be loaded from the relative URL: "/PartnerAccountService/partneraccount" (HTTP-GET) The data source for the [LocationCity] select control should be loaded from the relative URL: "/LocationCityService/locationcity" (HTTP-GET) An existing CarRentalLocation entity should be loaded from the relative URL: "/CarRentalLocationService/carrentallocation/{id}" (HTTP-GET) If a new CarRentalLocation entity has been created, the new entity should be posted to the relative URL: "/CarRentalLocationService/carrentallocation" (HTTP-POST) If an existing CarRentalLocation entity has been updated, the modified entity should be sent to the relative URL: "/CarRentalLocationService/carrentallocation/{id}" (HTTP-PUT) If an existing CarRentalLocation entity has to be deleted, the following relative URL should be called: "/CarRentalLocationService/carrentallocation/{id}" (HTTP-DELETE) Add a HTML table to the view with the following CarRentalBooking columns: - column: TotalAmount - column: CarRentalProduct - column: DropoffLocation - column: DropoffDateTime - column: Booking - column: PickupLocation - column: Currency - column: PickupDateTime The table should have the title "CarRentalBookings" und the data must be loaded from the server with the following relative URL: "/CarRentalLocationService/carrentalbooking/pickuplocation/{id}" Add a HTML table to the view with the following CarRentalBooking columns: - column: TotalAmount - column: CarRentalProduct - column: DropoffLocation - column: DropoffDateTime - column: Booking - column: PickupLocation - column: Currency - column: PickupDateTime The table should have the title "CarRentalBookings" und the data must be loaded from the server with the following relative URL: "/CarRentalLocationService/carrentalbooking/dropofflocation/{id}" Add a HTML table to the view with the following CarRentalProduct columns: - column: CarRentalLocation - column: AirConditioning - column: Description - column: Transmission - column: Doors - column: Seats - column: Name - column: CarCategory The table should have the title "CarRentalProducts" und the data must be loaded from the server with the following relative URL: "/CarCategoryService/carrentalproduct/carrentallocation/{id}" 3. The RoomTypeCategoryView must contain the following fields: - name: Code type: STRING - name: Name type: STRING An existing RoomTypeCategory entity should be loaded from the relative URL: "/CarRentalLocationService/roomtypecategory/{id}" (HTTP-GET) If a new RoomTypeCategory entity has been created, the new entity should be posted to the relative URL: "/CarRentalLocationService/roomtypecategory" (HTTP-POST) If an existing RoomTypeCategory entity has been updated, the modified entity should be sent to the relative URL: "/CarRentalLocationService/roomtypecategory/{id}" (HTTP-PUT) If an existing RoomTypeCategory entity has to be deleted, the following relative URL should be called: "/CarRentalLocationService/roomtypecategory/{id}" (HTTP-DELETE) Add a HTML table to the view with the following RoomType columns: - column: MaxAdults - column: Property - column: SizeSquareMeters - column: RoomTypeCategory - column: BedConfiguration - column: MaxOccupancy - column: Description - column: Name - column: CreatedAt - column: MaxChildren The table should have the title "RoomTypes" und the data must be loaded from the server with the following relative URL: "/RoomTypeService/roomtype/roomtypecategory/{id}"
Copy prompt
Overview
Summary
Contact
Donate
Imprint