Prompt for the PropertyApp

Please create a React-JS application for the PropertyModule. The application  has to offer the following views for the user interface: 
    1. LocationDistrictView 
    2. PropertyView 
    3. PropertyAmenityView 
    4. PropertyPolicyView 
    5. PropertyTypeView 
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 LocationDistrictView must contain the following fields: 
    - name: LocationCity   type: LocationCity 
    - name: Name   type: STRING 
The data source for the [LocationCity] select control should be loaded from the relative URL: 
    "/LocationCityService/locationcity"   (HTTP-GET) 
An existing LocationDistrict entity should be loaded from the relative URL: 
    "/PropertyService/locationdistrict/{id}"   (HTTP-GET) 
If a new LocationDistrict entity has been created, the new entity should be posted to the relative URL: 
    "/PropertyService/locationdistrict"   (HTTP-POST) 
If an existing LocationDistrict entity has been updated, the modified entity should be sent to the relative URL: 
    "/PropertyService/locationdistrict/{id}"   (HTTP-PUT) 
If an existing LocationDistrict entity has to be deleted, the following relative URL should be called: 
    "/PropertyService/locationdistrict/{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/locationdistrict/{id}"

2. The PropertyView must contain the following fields: 
    - name: AddressLine1   type: STRING 
    - name: AddressLine2   type: STRING 
    - name: CheckInFrom   type: STRING 
    - name: CheckInTo   type: STRING 
    - name: CheckOutFrom   type: STRING 
    - name: CheckOutTo   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: IsActive   type: BOOL 
    - name: Latitude   type: STRING 
    - name: LocationCity   type: LocationCity 
    - name: LocationCountry   type: LocationCountry 
    - name: LocationDistrict   type: LocationDistrict 
    - name: Longitude   type: STRING 
    - name: Name   type: STRING 
    - name: PartnerAccount   type: PartnerAccount 
    - name: PostalCode   type: STRING 
    - name: PropertyType   type: PropertyType 
    - name: StarRating   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 [LocationCountry] select control should be loaded from the relative URL: 
    "/LocationCityService/locationcountry"   (HTTP-GET) 
The data source for the [LocationDistrict] select control should be loaded from the relative URL: 
    "/PropertyService/locationdistrict"   (HTTP-GET) 
The data source for the [LocationCity] select control should be loaded from the relative URL: 
    "/LocationCityService/locationcity"   (HTTP-GET) 
The data source for the [PropertyType] select control should be loaded from the relative URL: 
    "/PropertyService/propertytype"   (HTTP-GET) 
An existing Property entity should be loaded from the relative URL: 
    "/PropertyService/property/{id}"   (HTTP-GET) 
If a new Property entity has been created, the new entity should be posted to the relative URL: 
    "/PropertyService/property"   (HTTP-POST) 
If an existing Property entity has been updated, the modified entity should be sent to the relative URL: 
    "/PropertyService/property/{id}"   (HTTP-PUT) 
If an existing Property entity has to be deleted, the following relative URL should be called: 
    "/PropertyService/property/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following PropertyPolicy columns: 
    - column: CancellationPolicy 
    - column: CheckOutPolicy 
    - column: PetsPolicy 
    - column: OtherPolicy 
    - column: CheckInPolicy 
    - column: Property 
    - column: ChildrenPolicy 
The table should have the title "PropertyPolicys" und the data must be loaded from the server with the following relative URL: 
    "/PropertyService/propertypolicy/property/{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/property/{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/property/{id}" 
Add a HTML table to the view with the following Review columns: 
    - column: Attraction 
    - column: Text 
    - column: UserAccount 
    - column: Property 
    - column: Booking 
    - column: Language 
    - column: OverallScore 
    - column: AirportTransferProduct 
    - column: CarRentalProduct 
    - column: IsPublic 
    - column: Title 
    - column: CreatedAt 
The table should have the title "Reviews" und the data must be loaded from the server with the following relative URL: 
    "/LanguageService/review/property/{id}" 
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/property/{id}" 
Add a HTML table to the view with the following PropertyPhoto columns: 
    - column: IsMain 
    - column: Url 
    - column: Caption 
    - column: SortOrder 
    - column: Property 
The table should have the title "PropertyPhotos" und the data must be loaded from the server with the following relative URL: 
    "/AttractionBookingService/propertyphoto/property/{id}"

3. The PropertyAmenityView must contain the following fields: 
    - name: AdditionalInfo   type: STRING 
    - name: Amenity   type: Amenity 
    - name: IsFree   type: BOOL 
    - name: Property   type: Property 
The data source for the [Amenity] select control should be loaded from the relative URL: 
    "/RoomTypeService/amenity"   (HTTP-GET) 
The data source for the [Property] select control should be loaded from the relative URL: 
    "/PropertyService/property"   (HTTP-GET) 
An existing PropertyAmenity entity should be loaded from the relative URL: 
    "/PropertyService/propertyamenity/{id}"   (HTTP-GET) 
If a new PropertyAmenity entity has been created, the new entity should be posted to the relative URL: 
    "/PropertyService/propertyamenity"   (HTTP-POST) 
If an existing PropertyAmenity entity has been updated, the modified entity should be sent to the relative URL: 
    "/PropertyService/propertyamenity/{id}"   (HTTP-PUT) 
If an existing PropertyAmenity entity has to be deleted, the following relative URL should be called: 
    "/PropertyService/propertyamenity/{id}"   (HTTP-DELETE)

4. The PropertyPolicyView must contain the following fields: 
    - name: CancellationPolicy   type: STRING 
    - name: CheckInPolicy   type: STRING 
    - name: CheckOutPolicy   type: STRING 
    - name: ChildrenPolicy   type: STRING 
    - name: OtherPolicy   type: STRING 
    - name: PetsPolicy   type: STRING 
    - name: Property   type: Property 
The data source for the [Property] select control should be loaded from the relative URL: 
    "/PropertyService/property"   (HTTP-GET) 
An existing PropertyPolicy entity should be loaded from the relative URL: 
    "/PropertyService/propertypolicy/{id}"   (HTTP-GET) 
If a new PropertyPolicy entity has been created, the new entity should be posted to the relative URL: 
    "/PropertyService/propertypolicy"   (HTTP-POST) 
If an existing PropertyPolicy entity has been updated, the modified entity should be sent to the relative URL: 
    "/PropertyService/propertypolicy/{id}"   (HTTP-PUT) 
If an existing PropertyPolicy entity has to be deleted, the following relative URL should be called: 
    "/PropertyService/propertypolicy/{id}"   (HTTP-DELETE)

5. The PropertyTypeView must contain the following fields: 
    - name: Code   type: STRING 
    - name: Name   type: STRING 
An existing PropertyType entity should be loaded from the relative URL: 
    "/PropertyService/propertytype/{id}"   (HTTP-GET) 
If a new PropertyType entity has been created, the new entity should be posted to the relative URL: 
    "/PropertyService/propertytype"   (HTTP-POST) 
If an existing PropertyType entity has been updated, the modified entity should be sent to the relative URL: 
    "/PropertyService/propertytype/{id}"   (HTTP-PUT) 
If an existing PropertyType entity has to be deleted, the following relative URL should be called: 
    "/PropertyService/propertytype/{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/propertytype/{id}"