Prompt for the PriceCategoryApp

Please create a React-JS application for the PriceCategoryModule. The application  has to offer the following views for the user interface: 
    1. EventTicketTypeView 
    2. PriceCategoryView 
    3. TicketTypeView 
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 EventTicketTypeView must contain the following fields: 
    - name: BasePrice   type: STRING 
    - name: Event   type: Event 
    - name: IsActive   type: BOOL 
    - name: PriceCategory   type: PriceCategory 
    - name: SeatBlock   type: SeatBlock 
    - name: SoldQuantity   type: LONG 
    - name: TicketType   type: TicketType 
    - name: TotalAllocation   type: LONG 
    - name: VenueArea   type: VenueArea 
The data source for the [SeatBlock] select control should be loaded from the relative URL: 
    "/VenueAreaService/seatblock"   (HTTP-GET) 
The data source for the [Event] select control should be loaded from the relative URL: 
    "/EventService/event"   (HTTP-GET) 
The data source for the [PriceCategory] select control should be loaded from the relative URL: 
    "/PriceCategoryService/pricecategory"   (HTTP-GET) 
The data source for the [VenueArea] select control should be loaded from the relative URL: 
    "/VenueAreaService/venuearea"   (HTTP-GET) 
The data source for the [TicketType] select control should be loaded from the relative URL: 
    "/PriceCategoryService/tickettype"   (HTTP-GET) 
An existing EventTicketType entity should be loaded from the relative URL: 
    "/PriceCategoryService/eventtickettype/{id}"   (HTTP-GET) 
If a new EventTicketType entity has been created, the new entity should be posted to the relative URL: 
    "/PriceCategoryService/eventtickettype"   (HTTP-POST) 
If an existing EventTicketType entity has been updated, the modified entity should be sent to the relative URL: 
    "/PriceCategoryService/eventtickettype/{id}"   (HTTP-PUT) 
If an existing EventTicketType entity has to be deleted, the following relative URL should be called: 
    "/PriceCategoryService/eventtickettype/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following BookingItem columns: 
    - column: Quantity 
    - column: Event 
    - column: Seat 
    - column: UnitPrice 
    - column: EventTicketType 
    - column: Booking 
    - column: TotalPrice 
The table should have the title "BookingItems" und the data must be loaded from the server with the following relative URL: 
    "/EventService/bookingitem/eventtickettype/{id}"

2. The PriceCategoryView must contain the following fields: 
    - name: Code   type: STRING 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
An existing PriceCategory entity should be loaded from the relative URL: 
    "/PriceCategoryService/pricecategory/{id}"   (HTTP-GET) 
If a new PriceCategory entity has been created, the new entity should be posted to the relative URL: 
    "/PriceCategoryService/pricecategory"   (HTTP-POST) 
If an existing PriceCategory entity has been updated, the modified entity should be sent to the relative URL: 
    "/PriceCategoryService/pricecategory/{id}"   (HTTP-PUT) 
If an existing PriceCategory entity has to be deleted, the following relative URL should be called: 
    "/PriceCategoryService/pricecategory/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following EventTicketType columns: 
    - column: VenueArea 
    - column: SoldQuantity 
    - column: TicketType 
    - column: SeatBlock 
    - column: IsActive 
    - column: TotalAllocation 
    - column: Event 
    - column: PriceCategory 
    - column: BasePrice 
The table should have the title "EventTicketTypes" und the data must be loaded from the server with the following relative URL: 
    "/PriceCategoryService/eventtickettype/pricecategory/{id}"

3. The TicketTypeView must contain the following fields: 
    - name: Description   type: STRING 
    - name: IsSeated   type: BOOL 
    - name: Name   type: STRING 
An existing TicketType entity should be loaded from the relative URL: 
    "/PriceCategoryService/tickettype/{id}"   (HTTP-GET) 
If a new TicketType entity has been created, the new entity should be posted to the relative URL: 
    "/PriceCategoryService/tickettype"   (HTTP-POST) 
If an existing TicketType entity has been updated, the modified entity should be sent to the relative URL: 
    "/PriceCategoryService/tickettype/{id}"   (HTTP-PUT) 
If an existing TicketType entity has to be deleted, the following relative URL should be called: 
    "/PriceCategoryService/tickettype/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following EventTicketType columns: 
    - column: VenueArea 
    - column: SoldQuantity 
    - column: TicketType 
    - column: SeatBlock 
    - column: IsActive 
    - column: TotalAllocation 
    - column: Event 
    - column: PriceCategory 
    - column: BasePrice 
The table should have the title "EventTicketTypes" und the data must be loaded from the server with the following relative URL: 
    "/PriceCategoryService/eventtickettype/tickettype/{id}"