Prompt for the AttractionBookingApp

Please create a React-JS application for the AttractionBookingModule. The application  has to offer the following views for the user interface: 
    1. AttractionBookingView 
    2. AttractionParticipantView 
    3. PropertyPhotoView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 3 views are defined below.

1. The AttractionBookingView must contain the following fields: 
    - name: Adults   type: INT 
    - name: AttractionSchedule   type: AttractionSchedule 
    - name: Booking   type: Booking 
    - name: Children   type: INT 
    - name: Currency   type: Currency 
    - name: TotalAmount   type: STRING 
The data source for the [Currency] select control should be loaded from the relative URL: 
    "/CurrencyService/currency"   (HTTP-GET) 
The data source for the [Booking] select control should be loaded from the relative URL: 
    "/BookingService/booking"   (HTTP-GET) 
The data source for the [AttractionSchedule] select control should be loaded from the relative URL: 
    "/PartnerAccountService/attractionschedule"   (HTTP-GET) 
An existing AttractionBooking entity should be loaded from the relative URL: 
    "/AttractionBookingService/attractionbooking/{id}"   (HTTP-GET) 
If a new AttractionBooking entity has been created, the new entity should be posted to the relative URL: 
    "/AttractionBookingService/attractionbooking"   (HTTP-POST) 
If an existing AttractionBooking entity has been updated, the modified entity should be sent to the relative URL: 
    "/AttractionBookingService/attractionbooking/{id}"   (HTTP-PUT) 
If an existing AttractionBooking entity has to be deleted, the following relative URL should be called: 
    "/AttractionBookingService/attractionbooking/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following AttractionParticipant columns: 
    - column: IsPrimary 
    - column: AttractionBooking 
    - column: Age 
    - column: FullName 
The table should have the title "AttractionParticipants" und the data must be loaded from the server with the following relative URL: 
    "/AttractionBookingService/attractionparticipant/attractionbooking/{id}"

2. The AttractionParticipantView must contain the following fields: 
    - name: Age   type: INT 
    - name: AttractionBooking   type: AttractionBooking 
    - name: FullName   type: STRING 
    - name: IsPrimary   type: BOOL 
The data source for the [AttractionBooking] select control should be loaded from the relative URL: 
    "/AttractionBookingService/attractionbooking"   (HTTP-GET) 
An existing AttractionParticipant entity should be loaded from the relative URL: 
    "/AttractionBookingService/attractionparticipant/{id}"   (HTTP-GET) 
If a new AttractionParticipant entity has been created, the new entity should be posted to the relative URL: 
    "/AttractionBookingService/attractionparticipant"   (HTTP-POST) 
If an existing AttractionParticipant entity has been updated, the modified entity should be sent to the relative URL: 
    "/AttractionBookingService/attractionparticipant/{id}"   (HTTP-PUT) 
If an existing AttractionParticipant entity has to be deleted, the following relative URL should be called: 
    "/AttractionBookingService/attractionparticipant/{id}"   (HTTP-DELETE)

3. The PropertyPhotoView must contain the following fields: 
    - name: Caption   type: STRING 
    - name: IsMain   type: BOOL 
    - name: Property   type: Property 
    - name: SortOrder   type: INT 
    - name: Url   type: STRING 
The data source for the [Property] select control should be loaded from the relative URL: 
    "/PropertyService/property"   (HTTP-GET) 
An existing PropertyPhoto entity should be loaded from the relative URL: 
    "/AttractionBookingService/propertyphoto/{id}"   (HTTP-GET) 
If a new PropertyPhoto entity has been created, the new entity should be posted to the relative URL: 
    "/AttractionBookingService/propertyphoto"   (HTTP-POST) 
If an existing PropertyPhoto entity has been updated, the modified entity should be sent to the relative URL: 
    "/AttractionBookingService/propertyphoto/{id}"   (HTTP-PUT) 
If an existing PropertyPhoto entity has to be deleted, the following relative URL should be called: 
    "/AttractionBookingService/propertyphoto/{id}"   (HTTP-DELETE)