Prompt for the HostProfileApp

Please create a React-JS application for the HostProfileModule. The application  has to offer the following views for the user interface: 
    1. AvailabilityCalendarView 
    2. HostProfileView 
    3. ListingPhotoView 
    4. PayoutView 
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 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: 
    "/HostProfileService/availabilitycalendar/{id}"   (HTTP-GET) 
If a new AvailabilityCalendar entity has been created, the new entity should be posted to the relative URL: 
    "/HostProfileService/availabilitycalendar"   (HTTP-POST) 
If an existing AvailabilityCalendar entity has been updated, the modified entity should be sent to the relative URL: 
    "/HostProfileService/availabilitycalendar/{id}"   (HTTP-PUT) 
If an existing AvailabilityCalendar entity has to be deleted, the following relative URL should be called: 
    "/HostProfileService/availabilitycalendar/{id}"   (HTTP-DELETE)

2. The HostProfileView must contain the following fields: 
    - name: About   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: IsSuperhost   type: BOOL 
    - name: OverallRating   type: DOUBLE 
    - name: PlatformUser   type: PlatformUser 
    - name: ResponseRate   type: DOUBLE 
    - name: ResponseTime   type: STRING 
    - name: SuperhostSince   type: DATE 
The data source for the [PlatformUser] select control should be loaded from the relative URL: 
    "/PlatformUserService/platformuser"   (HTTP-GET) 
An existing HostProfile entity should be loaded from the relative URL: 
    "/HostProfileService/hostprofile/{id}"   (HTTP-GET) 
If a new HostProfile entity has been created, the new entity should be posted to the relative URL: 
    "/HostProfileService/hostprofile"   (HTTP-POST) 
If an existing HostProfile entity has been updated, the modified entity should be sent to the relative URL: 
    "/HostProfileService/hostprofile/{id}"   (HTTP-PUT) 
If an existing HostProfile entity has to be deleted, the following relative URL should be called: 
    "/HostProfileService/hostprofile/{id}"   (HTTP-DELETE) 
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/hostprofile/{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/hostprofile/{id}"

3. The ListingPhotoView must contain the following fields: 
    - name: Caption   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: Listing   type: Listing 
    - name: SortOrder   type: INT 
    - name: Url   type: STRING 
The data source for the [Listing] select control should be loaded from the relative URL: 
    "/ListingService/listing"   (HTTP-GET) 
An existing ListingPhoto entity should be loaded from the relative URL: 
    "/HostProfileService/listingphoto/{id}"   (HTTP-GET) 
If a new ListingPhoto entity has been created, the new entity should be posted to the relative URL: 
    "/HostProfileService/listingphoto"   (HTTP-POST) 
If an existing ListingPhoto entity has been updated, the modified entity should be sent to the relative URL: 
    "/HostProfileService/listingphoto/{id}"   (HTTP-PUT) 
If an existing ListingPhoto entity has to be deleted, the following relative URL should be called: 
    "/HostProfileService/listingphoto/{id}"   (HTTP-DELETE)

4. The PayoutView must contain the following fields: 
    - name: Amount   type: DOUBLE 
    - name: Booking   type: Booking 
    - name: Currency   type: STRING 
    - name: HostProfile   type: HostProfile 
    - name: PayoutDate   type: DATE 
    - name: PayoutMethod   type: STRING 
    - name: PayoutStatus   type: STRING 
The data source for the [HostProfile] select control should be loaded from the relative URL: 
    "/HostProfileService/hostprofile"   (HTTP-GET) 
The data source for the [Booking] select control should be loaded from the relative URL: 
    "/BookingService/booking"   (HTTP-GET) 
An existing Payout entity should be loaded from the relative URL: 
    "/HostProfileService/payout/{id}"   (HTTP-GET) 
If a new Payout entity has been created, the new entity should be posted to the relative URL: 
    "/HostProfileService/payout"   (HTTP-POST) 
If an existing Payout entity has been updated, the modified entity should be sent to the relative URL: 
    "/HostProfileService/payout/{id}"   (HTTP-PUT) 
If an existing Payout entity has to be deleted, the following relative URL should be called: 
    "/HostProfileService/payout/{id}"   (HTTP-DELETE)