Overview
Summary
Services
Contact
Donate
About
Imprint
Prompt for the
ListingApp
Please create a React-JS application for the ListingModule. The application has to offer the following views for the user interface: 1. AvailabilityCalendarView 2. BookingView 3. CityView 4. FraudCaseView 5. HomeSharingClubView 6. ListingView The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 6 views are defined below. 1. The AvailabilityCalendarView must contain the following fields: - name: Currency type: STRING - name: Date type: DATE - name: IsAvailable type: BOOL - name: Listing type: Listing - name: MaximumNights type: INT - name: MinimumNights type: INT - name: PricePerNight type: DOUBLE The data source for the [Listing] select control should be loaded from the relative URL: "/ListingService/listing" (HTTP-GET) An existing AvailabilityCalendar entity should be loaded from the relative URL: "/ListingService/availabilitycalendar/{id}" (HTTP-GET) If a new AvailabilityCalendar entity has been created, the new entity should be posted to the relative URL: "/ListingService/availabilitycalendar" (HTTP-POST) If an existing AvailabilityCalendar entity has been updated, the modified entity should be sent to the relative URL: "/ListingService/availabilitycalendar/{id}" (HTTP-PUT) If an existing AvailabilityCalendar entity has to be deleted, the following relative URL should be called: "/ListingService/availabilitycalendar/{id}" (HTTP-DELETE) 2. The BookingView must contain the following fields: - name: BookingStatus type: STRING - name: CancellationPolicy type: STRING - name: CancelledAt type: DATE - name: CheckInDate type: DATE - name: CheckOutDate type: DATE - name: CleaningFee type: DOUBLE - name: ConfirmedAt type: DATE - name: CreatedAt type: DATE - name: Currency type: STRING - name: GuestProfile type: GuestProfile - name: Listing type: Listing - name: NumberOfGuests type: INT - name: ServiceFeeGuest type: DOUBLE - name: ServiceFeeHost type: DOUBLE - name: TotalPrice type: DOUBLE The data source for the [GuestProfile] select control should be loaded from the relative URL: "/PlatformUserService/guestprofile" (HTTP-GET) The data source for the [Listing] select control should be loaded from the relative URL: "/ListingService/listing" (HTTP-GET) An existing Booking entity should be loaded from the relative URL: "/ListingService/booking/{id}" (HTTP-GET) If a new Booking entity has been created, the new entity should be posted to the relative URL: "/ListingService/booking" (HTTP-POST) If an existing Booking entity has been updated, the modified entity should be sent to the relative URL: "/ListingService/booking/{id}" (HTTP-PUT) If an existing Booking entity has to be deleted, the following relative URL should be called: "/ListingService/booking/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Review columns: - column: RatingLocation - column: RatingValue - column: RatingCommunication - column: RatingOverall - column: Reviewee - column: Reviewer - column: ReviewType - column: CreatedAt - column: Booking - column: Comment - column: RatingCleanliness The table should have the title "Reviews" und the data must be loaded from the server with the following relative URL: "/AmenityService/review/booking/{id}" Add a HTML table to the view with the following Payout columns: - column: Booking - column: PayoutDate - column: Amount - column: PayoutMethod - column: HostProfile - column: PayoutStatus - column: Currency The table should have the title "Payouts" und the data must be loaded from the server with the following relative URL: "/HostProfileService/payout/booking/{id}" Add a HTML table to the view with the following Payment columns: - column: Booking - column: PaymentStatus - column: PaidAt - column: Currency - column: ExternalTransactionReference - column: PlatformUser - column: Amount - column: PaymentMethod The table should have the title "Payments" und the data must be loaded from the server with the following relative URL: "/PlatformUserService/payment/booking/{id}" 3. The CityView must contain the following fields: - name: Country type: Country - name: Latitude type: DOUBLE - name: Longitude type: DOUBLE - name: Name type: STRING - name: Region type: STRING The data source for the [Country] select control should be loaded from the relative URL: "/CountryService/country" (HTTP-GET) An existing City entity should be loaded from the relative URL: "/ListingService/city/{id}" (HTTP-GET) If a new City entity has been created, the new entity should be posted to the relative URL: "/ListingService/city" (HTTP-POST) If an existing City entity has been updated, the modified entity should be sent to the relative URL: "/ListingService/city/{id}" (HTTP-PUT) If an existing City entity has to be deleted, the following relative URL should be called: "/ListingService/city/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Market columns: - column: RegionName - column: IsKeyMarket - column: City - column: Country The table should have the title "Markets" und the data must be loaded from the server with the following relative URL: "/CountryService/market/city/{id}" Add a HTML table to the view with the following HomeSharingClub columns: - column: Description - column: Country - column: City - column: SupportedByCompany - column: FoundedDate The table should have the title "HomeSharingClubs" und the data must be loaded from the server with the following relative URL: "/ListingService/homesharingclub/city/{id}" Add a HTML table to the view with the following Office columns: - column: IsHeadquarters - column: Company - column: Country - column: AddressLine - column: City - column: OpenedDate - column: ClosedDate The table should have the title "Offices" und the data must be loaded from the server with the following relative URL: "/CompanyService/office/city/{id}" Add a HTML table to the view with the following Listing columns: - column: PostalCode - column: UpdatedAt - column: IsInstantBookable - column: PropertyType - column: Title - column: Status - column: Country - column: City - column: Bathrooms - column: CreatedAt - column: AddressLine - column: Beds - column: Bedrooms - column: MaxGuests - column: Latitude - column: HostProfile - column: Description - column: RoomType - column: Longitude The table should have the title "Listings" und the data must be loaded from the server with the following relative URL: "/ListingService/listing/city/{id}" Add a HTML table to the view with the following PlatformUser columns: - column: FacebookProfileUrl - column: CreatedAt - column: City - column: FullName - column: Country - column: UpdatedAt - column: PhoneNumber - column: Email - column: DateOfBirth - column: VerificationLevel - column: GoogleProfileUrl - column: ProfilePhotoUrl - column: LinkedinProfileUrl The table should have the title "PlatformUsers" und the data must be loaded from the server with the following relative URL: "/PlatformUserService/platformuser/city/{id}" Add a HTML table to the view with the following Company columns: - column: Website - column: Industry - column: Name - column: HeadquartersAddress - column: IsPublic - column: FoundedDate - column: Country - column: City - column: LegalForm The table should have the title "Companys" und the data must be loaded from the server with the following relative URL: "/CompanyService/company/city/{id}" 4. The FraudCaseView must contain the following fields: - name: CaseType type: STRING - name: Description type: STRING - name: Listing type: Listing - name: PlatformUserReporter type: PlatformUser - name: ReportedAt type: DATE - name: ResolvedAt type: DATE - name: Status type: STRING The data source for the [Listing] select control should be loaded from the relative URL: "/ListingService/listing" (HTTP-GET) The data source for the [PlatformUserReporter] select control should be loaded from the relative URL: "/PlatformUserService/platformuser" (HTTP-GET) An existing FraudCase entity should be loaded from the relative URL: "/ListingService/fraudcase/{id}" (HTTP-GET) If a new FraudCase entity has been created, the new entity should be posted to the relative URL: "/ListingService/fraudcase" (HTTP-POST) If an existing FraudCase entity has been updated, the modified entity should be sent to the relative URL: "/ListingService/fraudcase/{id}" (HTTP-PUT) If an existing FraudCase entity has to be deleted, the following relative URL should be called: "/ListingService/fraudcase/{id}" (HTTP-DELETE) 5. The HomeSharingClubView must contain the following fields: - name: City type: City - name: Country type: Country - name: Description type: STRING - name: FoundedDate type: DATE - name: SupportedByCompany type: LONG The data source for the [Country] select control should be loaded from the relative URL: "/CountryService/country" (HTTP-GET) The data source for the [City] select control should be loaded from the relative URL: "/ListingService/city" (HTTP-GET) An existing HomeSharingClub entity should be loaded from the relative URL: "/ListingService/homesharingclub/{id}" (HTTP-GET) If a new HomeSharingClub entity has been created, the new entity should be posted to the relative URL: "/ListingService/homesharingclub" (HTTP-POST) If an existing HomeSharingClub entity has been updated, the modified entity should be sent to the relative URL: "/ListingService/homesharingclub/{id}" (HTTP-PUT) If an existing HomeSharingClub entity has to be deleted, the following relative URL should be called: "/ListingService/homesharingclub/{id}" (HTTP-DELETE) 6. The ListingView must contain the following fields: - name: AddressLine type: STRING - name: Bathrooms type: DOUBLE - name: Bedrooms type: INT - name: Beds type: INT - name: City type: City - name: Country type: Country - name: CreatedAt type: DATE - name: Description type: STRING - name: HostProfile type: HostProfile - name: IsInstantBookable type: BOOL - name: Latitude type: DOUBLE - name: Longitude type: DOUBLE - name: MaxGuests type: INT - name: PostalCode type: STRING - name: PropertyType type: STRING - name: RoomType type: STRING - name: Status type: STRING - name: Title type: STRING - name: UpdatedAt type: DATE The data source for the [HostProfile] select control should be loaded from the relative URL: "/HostProfileService/hostprofile" (HTTP-GET) The data source for the [Country] select control should be loaded from the relative URL: "/CountryService/country" (HTTP-GET) The data source for the [City] select control should be loaded from the relative URL: "/ListingService/city" (HTTP-GET) An existing Listing entity should be loaded from the relative URL: "/ListingService/listing/{id}" (HTTP-GET) If a new Listing entity has been created, the new entity should be posted to the relative URL: "/ListingService/listing" (HTTP-POST) If an existing Listing entity has been updated, the modified entity should be sent to the relative URL: "/ListingService/listing/{id}" (HTTP-PUT) If an existing Listing entity has to be deleted, the following relative URL should be called: "/ListingService/listing/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Booking columns: - column: CleaningFee - column: Listing - column: CheckInDate - column: BookingStatus - column: GuestProfile - column: CreatedAt - column: CancellationPolicy - column: CheckOutDate - column: ServiceFeeGuest - column: TotalPrice - column: ServiceFeeHost - column: CancelledAt - column: Currency - column: ConfirmedAt - column: NumberOfGuests The table should have the title "Bookings" und the data must be loaded from the server with the following relative URL: "/ListingService/booking/listing/{id}" Add a HTML table to the view with the following AvailabilityCalendar columns: - column: IsAvailable - column: Listing - column: MaximumNights - column: Date - column: PricePerNight - column: Currency - column: MinimumNights The table should have the title "AvailabilityCalendars" und the data must be loaded from the server with the following relative URL: "/ListingService/availabilitycalendar/listing/{id}" Add a HTML table to the view with the following MessageThread columns: - column: CreatedAt - column: Listing The table should have the title "MessageThreads" und the data must be loaded from the server with the following relative URL: "/MessageThreadService/messagethread/listing/{id}" Add a HTML table to the view with the following ListingPhoto columns: - column: CreatedAt - column: Url - column: SortOrder - column: Caption - column: Listing The table should have the title "ListingPhotos" und the data must be loaded from the server with the following relative URL: "/HostProfileService/listingphoto/listing/{id}" Add a HTML table to the view with the following ListingAmenity columns: - column: Listing - column: Amenity The table should have the title "ListingAmenitys" und the data must be loaded from the server with the following relative URL: "/AmenityService/listingamenity/listing/{id}" Add a HTML table to the view with the following StockListing columns: - column: Exchange - column: Isin - column: ListingDate - column: Segment - column: Ticker - column: Company The table should have the title "StockListings" und the data must be loaded from the server with the following relative URL: "/CompanyService/stocklisting/listingdate/{id}" Add a HTML table to the view with the following FraudCase columns: - column: PlatformUserReporter - column: ResolvedAt - column: Status - column: Listing - column: CaseType - column: Description - column: ReportedAt The table should have the title "FraudCases" und the data must be loaded from the server with the following relative URL: "/ListingService/fraudcase/listing/{id}" Add a HTML table to the view with the following HiddenCameraIncident columns: - column: SettlementType - column: ReportedAt - column: Description - column: InvolvedGuests - column: LawEnforcementContacted - column: Listing The table should have the title "HiddenCameraIncidents" und the data must be loaded from the server with the following relative URL: "/AmenityService/hiddencameraincident/listing/{id}"
Copy prompt
Overview
Summary
Services
Contact
Donate
About
Imprint