Overview
Summary
Contact
Donate
Imprint
Prompt for the
RoomTypeApp
Please create a React-JS application for the RoomTypeModule. The application has to offer the following views for the user interface: 1. AmenityView 2. RoomTypeView 3. RoomTypeAmenityView 4. RoomTypePhotoView 5. RoomUnitView 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 AmenityView must contain the following fields: - name: Code type: STRING - name: Description type: STRING - name: Name type: STRING An existing Amenity entity should be loaded from the relative URL: "/RoomTypeService/amenity/{id}" (HTTP-GET) If a new Amenity entity has been created, the new entity should be posted to the relative URL: "/RoomTypeService/amenity" (HTTP-POST) If an existing Amenity entity has been updated, the modified entity should be sent to the relative URL: "/RoomTypeService/amenity/{id}" (HTTP-PUT) If an existing Amenity entity has to be deleted, the following relative URL should be called: "/RoomTypeService/amenity/{id}" (HTTP-DELETE) Add a HTML table to the view with the following RoomTypeAmenity columns: - column: AdditionalInfo - column: Amenity - column: RoomType The table should have the title "RoomTypeAmenitys" und the data must be loaded from the server with the following relative URL: "/RoomTypeService/roomtypeamenity/amenity/{id}" Add a HTML table to the view with the following PropertyAmenity columns: - column: AdditionalInfo - column: Property - column: Amenity - column: IsFree The table should have the title "PropertyAmenitys" und the data must be loaded from the server with the following relative URL: "/PropertyService/propertyamenity/amenity/{id}" 2. The RoomTypeView must contain the following fields: - name: BedConfiguration type: STRING - name: CreatedAt type: DATE - name: Description type: STRING - name: MaxAdults type: INT - name: MaxChildren type: INT - name: MaxOccupancy type: INT - name: Name type: STRING - name: Property type: Property - name: RoomTypeCategory type: RoomTypeCategory - name: SizeSquareMeters type: STRING The data source for the [RoomTypeCategory] select control should be loaded from the relative URL: "/CarRentalLocationService/roomtypecategory" (HTTP-GET) The data source for the [Property] select control should be loaded from the relative URL: "/PropertyService/property" (HTTP-GET) An existing RoomType entity should be loaded from the relative URL: "/RoomTypeService/roomtype/{id}" (HTTP-GET) If a new RoomType entity has been created, the new entity should be posted to the relative URL: "/RoomTypeService/roomtype" (HTTP-POST) If an existing RoomType entity has been updated, the modified entity should be sent to the relative URL: "/RoomTypeService/roomtype/{id}" (HTTP-PUT) If an existing RoomType entity has to be deleted, the following relative URL should be called: "/RoomTypeService/roomtype/{id}" (HTTP-DELETE) Add a HTML table to the view with the following RoomTypeAmenity columns: - column: AdditionalInfo - column: Amenity - column: RoomType The table should have the title "RoomTypeAmenitys" und the data must be loaded from the server with the following relative URL: "/RoomTypeService/roomtypeamenity/roomtype/{id}" Add a HTML table to the view with the following StayBooking columns: - column: Booking - column: CheckOutDate - column: RoomType - column: Adults - column: Children - column: SpecialRequests - column: NumberOfRooms - column: RoomRatePlan - column: CheckInDate - column: BaseAmount - column: Currency - column: CancellationPolicySnapshot - column: TaxesAmount - column: Property - column: FeesAmount The table should have the title "StayBookings" und the data must be loaded from the server with the following relative URL: "/StayBookingService/staybooking/roomtype/{id}" Add a HTML table to the view with the following RoomTypePhoto columns: - column: Url - column: Caption - column: SortOrder - column: RoomType The table should have the title "RoomTypePhotos" und the data must be loaded from the server with the following relative URL: "/RoomTypeService/roomtypephoto/roomtype/{id}" Add a HTML table to the view with the following RoomUnit columns: - column: UnitCode - column: RoomType - column: IsActive The table should have the title "RoomUnits" und the data must be loaded from the server with the following relative URL: "/RoomTypeService/roomunit/roomtype/{id}" Add a HTML table to the view with the following RoomAvailability columns: - column: ClosedForDeparture - column: ClosedForArrival - column: RoomType - column: SoldInventory - column: TotalInventory - column: Date The table should have the title "RoomAvailabilitys" und the data must be loaded from the server with the following relative URL: "/CarCategoryService/roomavailability/roomtype/{id}" Add a HTML table to the view with the following RoomRatePlan columns: - column: MinimumStayNights - column: FreeCancellationUntilDays - column: CreatedAt - column: Description - column: IsRefundable - column: IncludesBreakfast - column: RoomType - column: Name - column: MaximumStayNights The table should have the title "RoomRatePlans" und the data must be loaded from the server with the following relative URL: "/StayBookingService/roomrateplan/roomtype/{id}" 3. The RoomTypeAmenityView must contain the following fields: - name: AdditionalInfo type: STRING - name: Amenity type: Amenity - name: RoomType type: RoomType The data source for the [Amenity] select control should be loaded from the relative URL: "/RoomTypeService/amenity" (HTTP-GET) The data source for the [RoomType] select control should be loaded from the relative URL: "/RoomTypeService/roomtype" (HTTP-GET) An existing RoomTypeAmenity entity should be loaded from the relative URL: "/RoomTypeService/roomtypeamenity/{id}" (HTTP-GET) If a new RoomTypeAmenity entity has been created, the new entity should be posted to the relative URL: "/RoomTypeService/roomtypeamenity" (HTTP-POST) If an existing RoomTypeAmenity entity has been updated, the modified entity should be sent to the relative URL: "/RoomTypeService/roomtypeamenity/{id}" (HTTP-PUT) If an existing RoomTypeAmenity entity has to be deleted, the following relative URL should be called: "/RoomTypeService/roomtypeamenity/{id}" (HTTP-DELETE) 4. The RoomTypePhotoView must contain the following fields: - name: Caption type: STRING - name: RoomType type: RoomType - name: SortOrder type: INT - name: Url type: STRING The data source for the [RoomType] select control should be loaded from the relative URL: "/RoomTypeService/roomtype" (HTTP-GET) An existing RoomTypePhoto entity should be loaded from the relative URL: "/RoomTypeService/roomtypephoto/{id}" (HTTP-GET) If a new RoomTypePhoto entity has been created, the new entity should be posted to the relative URL: "/RoomTypeService/roomtypephoto" (HTTP-POST) If an existing RoomTypePhoto entity has been updated, the modified entity should be sent to the relative URL: "/RoomTypeService/roomtypephoto/{id}" (HTTP-PUT) If an existing RoomTypePhoto entity has to be deleted, the following relative URL should be called: "/RoomTypeService/roomtypephoto/{id}" (HTTP-DELETE) 5. The RoomUnitView must contain the following fields: - name: IsActive type: BOOL - name: RoomType type: RoomType - name: UnitCode type: STRING The data source for the [RoomType] select control should be loaded from the relative URL: "/RoomTypeService/roomtype" (HTTP-GET) An existing RoomUnit entity should be loaded from the relative URL: "/RoomTypeService/roomunit/{id}" (HTTP-GET) If a new RoomUnit entity has been created, the new entity should be posted to the relative URL: "/RoomTypeService/roomunit" (HTTP-POST) If an existing RoomUnit entity has been updated, the modified entity should be sent to the relative URL: "/RoomTypeService/roomunit/{id}" (HTTP-PUT) If an existing RoomUnit entity has to be deleted, the following relative URL should be called: "/RoomTypeService/roomunit/{id}" (HTTP-DELETE)
Copy prompt
Overview
Summary
Contact
Donate
Imprint