Prompt for the PartnerAccountApp

Please create a React-JS application for the PartnerAccountModule. The application  has to offer the following views for the user interface: 
    1. AirportTransferProviderView 
    2. AttractionView 
    3. AttractionScheduleView 
    4. PartnerAccountView 
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 AirportTransferProviderView must contain the following fields: 
    - name: ContactEmail   type: STRING 
    - name: ContactPhone   type: STRING 
    - name: Name   type: STRING 
    - name: PartnerAccount   type: PartnerAccount 
The data source for the [PartnerAccount] select control should be loaded from the relative URL: 
    "/PartnerAccountService/partneraccount"   (HTTP-GET) 
An existing AirportTransferProvider entity should be loaded from the relative URL: 
    "/PartnerAccountService/airporttransferprovider/{id}"   (HTTP-GET) 
If a new AirportTransferProvider entity has been created, the new entity should be posted to the relative URL: 
    "/PartnerAccountService/airporttransferprovider"   (HTTP-POST) 
If an existing AirportTransferProvider entity has been updated, the modified entity should be sent to the relative URL: 
    "/PartnerAccountService/airporttransferprovider/{id}"   (HTTP-PUT) 
If an existing AirportTransferProvider entity has to be deleted, the following relative URL should be called: 
    "/PartnerAccountService/airporttransferprovider/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following AirportTransferProduct columns: 
    - column: Description 
    - column: DestinationCity 
    - column: MaxPassengers 
    - column: VehicleType 
    - column: Name 
    - column: OriginAirport 
    - column: OriginCity 
    - column: DestinationAirport 
    - column: AirportTransferProvider 
The table should have the title "AirportTransferProducts" und the data must be loaded from the server with the following relative URL: 
    "/AirportService/airporttransferproduct/airporttransferprovider/{id}"

2. The AttractionView must contain the following fields: 
    - name: AddressLine1   type: STRING 
    - name: AddressLine2   type: STRING 
    - name: Description   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 Attraction entity should be loaded from the relative URL: 
    "/PartnerAccountService/attraction/{id}"   (HTTP-GET) 
If a new Attraction entity has been created, the new entity should be posted to the relative URL: 
    "/PartnerAccountService/attraction"   (HTTP-POST) 
If an existing Attraction entity has been updated, the modified entity should be sent to the relative URL: 
    "/PartnerAccountService/attraction/{id}"   (HTTP-PUT) 
If an existing Attraction entity has to be deleted, the following relative URL should be called: 
    "/PartnerAccountService/attraction/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following AttractionSchedule columns: 
    - column: EndDateTime 
    - column: StartDateTime 
    - column: Attraction 
    - column: Capacity 
The table should have the title "AttractionSchedules" und the data must be loaded from the server with the following relative URL: 
    "/PartnerAccountService/attractionschedule/attraction/{id}"

3. The AttractionScheduleView must contain the following fields: 
    - name: Attraction   type: Attraction 
    - name: Capacity   type: INT 
    - name: EndDateTime   type: DATE 
    - name: StartDateTime   type: DATE 
The data source for the [Attraction] select control should be loaded from the relative URL: 
    "/PartnerAccountService/attraction"   (HTTP-GET) 
An existing AttractionSchedule entity should be loaded from the relative URL: 
    "/PartnerAccountService/attractionschedule/{id}"   (HTTP-GET) 
If a new AttractionSchedule entity has been created, the new entity should be posted to the relative URL: 
    "/PartnerAccountService/attractionschedule"   (HTTP-POST) 
If an existing AttractionSchedule entity has been updated, the modified entity should be sent to the relative URL: 
    "/PartnerAccountService/attractionschedule/{id}"   (HTTP-PUT) 
If an existing AttractionSchedule entity has to be deleted, the following relative URL should be called: 
    "/PartnerAccountService/attractionschedule/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following AttractionBooking columns: 
    - column: TotalAmount 
    - column: Children 
    - column: Currency 
    - column: AttractionSchedule 
    - column: Booking 
    - column: Adults 
The table should have the title "AttractionBookings" und the data must be loaded from the server with the following relative URL: 
    "/AttractionBookingService/attractionbooking/attractionschedule/{id}"

4. The PartnerAccountView must contain the following fields: 
    - name: CompanyName   type: STRING 
    - name: ContactName   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: Email   type: STRING 
    - name: IsActive   type: BOOL 
    - name: PhoneNumber   type: STRING 
An existing PartnerAccount entity should be loaded from the relative URL: 
    "/PartnerAccountService/partneraccount/{id}"   (HTTP-GET) 
If a new PartnerAccount entity has been created, the new entity should be posted to the relative URL: 
    "/PartnerAccountService/partneraccount"   (HTTP-POST) 
If an existing PartnerAccount entity has been updated, the modified entity should be sent to the relative URL: 
    "/PartnerAccountService/partneraccount/{id}"   (HTTP-PUT) 
If an existing PartnerAccount entity has to be deleted, the following relative URL should be called: 
    "/PartnerAccountService/partneraccount/{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/partneraccount/{id}" 
Add a HTML table to the view with the following AirportTransferProvider columns: 
    - column: PartnerAccount 
    - column: Name 
    - column: ContactPhone 
    - column: ContactEmail 
The table should have the title "AirportTransferProviders" und the data must be loaded from the server with the following relative URL: 
    "/PartnerAccountService/airporttransferprovider/partneraccount/{id}" 
Add a HTML table to the view with the following CarRentalLocation columns: 
    - column: Latitude 
    - column: PostalCode 
    - column: Longitude 
    - column: AddressLine2 
    - column: LocationCity 
    - column: Name 
    - column: PartnerAccount 
    - column: AddressLine1 
The table should have the title "CarRentalLocations" und the data must be loaded from the server with the following relative URL: 
    "/CarRentalLocationService/carrentallocation/partneraccount/{id}" 
Add a HTML table to the view with the following Attraction columns: 
    - column: Description 
    - column: Name 
    - column: Latitude 
    - column: Longitude 
    - column: AddressLine2 
    - column: LocationCity 
    - column: PartnerAccount 
    - column: AddressLine1 
    - column: PostalCode 
The table should have the title "Attractions" und the data must be loaded from the server with the following relative URL: 
    "/PartnerAccountService/attraction/partneraccount/{id}"