Prompt for the MembershipTypeApp

Please create a React-JS application for the MembershipTypeModule. The application  has to offer the following views for the user interface: 
    1. MembershipTypeView 
    2. PriceItemView 
    3. PriceListView 
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 MembershipTypeView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: Description   type: STRING 
    - name: DurationMonths   type: LONG 
    - name: IsActive   type: BOOL 
    - name: MonthlyFee   type: STRING 
    - name: Name   type: STRING 
An existing MembershipType entity should be loaded from the relative URL: 
    "/MembershipTypeService/membershiptype/{id}"   (HTTP-GET) 
If a new MembershipType entity has been created, the new entity should be posted to the relative URL: 
    "/MembershipTypeService/membershiptype"   (HTTP-POST) 
If an existing MembershipType entity has been updated, the modified entity should be sent to the relative URL: 
    "/MembershipTypeService/membershiptype/{id}"   (HTTP-PUT) 
If an existing MembershipType entity has to be deleted, the following relative URL should be called: 
    "/MembershipTypeService/membershiptype/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Membership columns: 
    - column: MembershipType 
    - column: Status 
    - column: CreatedAt 
    - column: Customer 
    - column: EndDate 
    - column: AutoRenew 
    - column: StartDate 
The table should have the title "Memberships" und the data must be loaded from the server with the following relative URL: 
    "/CustomerService/membership/membershiptype/{id}" 
Add a HTML table to the view with the following PriceItem columns: 
    - column: MembershipType 
    - column: PriceList 
    - column: Sport 
    - column: CreatedAt 
    - column: TimeFrom 
    - column: PricePerHour 
    - column: TimeTo 
    - column: DayOfWeek 
    - column: BookingType 
The table should have the title "PriceItems" und the data must be loaded from the server with the following relative URL: 
    "/MembershipTypeService/priceitem/membershiptype/{id}"

2. The PriceItemView must contain the following fields: 
    - name: BookingType   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: DayOfWeek   type: LONG 
    - name: MembershipType   type: MembershipType 
    - name: PriceList   type: PriceList 
    - name: PricePerHour   type: STRING 
    - name: Sport   type: Sport 
    - name: TimeFrom   type: STRING 
    - name: TimeTo   type: STRING 
The data source for the [Sport] select control should be loaded from the relative URL: 
    "/SportService/sport"   (HTTP-GET) 
The data source for the [MembershipType] select control should be loaded from the relative URL: 
    "/MembershipTypeService/membershiptype"   (HTTP-GET) 
The data source for the [PriceList] select control should be loaded from the relative URL: 
    "/MembershipTypeService/pricelist"   (HTTP-GET) 
An existing PriceItem entity should be loaded from the relative URL: 
    "/MembershipTypeService/priceitem/{id}"   (HTTP-GET) 
If a new PriceItem entity has been created, the new entity should be posted to the relative URL: 
    "/MembershipTypeService/priceitem"   (HTTP-POST) 
If an existing PriceItem entity has been updated, the modified entity should be sent to the relative URL: 
    "/MembershipTypeService/priceitem/{id}"   (HTTP-PUT) 
If an existing PriceItem entity has to be deleted, the following relative URL should be called: 
    "/MembershipTypeService/priceitem/{id}"   (HTTP-DELETE)

3. The PriceListView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: Description   type: STRING 
    - name: IsActive   type: BOOL 
    - name: Name   type: STRING 
    - name: ValidFrom   type: DATE 
    - name: ValidTo   type: DATE 
An existing PriceList entity should be loaded from the relative URL: 
    "/MembershipTypeService/pricelist/{id}"   (HTTP-GET) 
If a new PriceList entity has been created, the new entity should be posted to the relative URL: 
    "/MembershipTypeService/pricelist"   (HTTP-POST) 
If an existing PriceList entity has been updated, the modified entity should be sent to the relative URL: 
    "/MembershipTypeService/pricelist/{id}"   (HTTP-PUT) 
If an existing PriceList entity has to be deleted, the following relative URL should be called: 
    "/MembershipTypeService/pricelist/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following PriceItem columns: 
    - column: MembershipType 
    - column: PriceList 
    - column: Sport 
    - column: CreatedAt 
    - column: TimeFrom 
    - column: PricePerHour 
    - column: TimeTo 
    - column: DayOfWeek 
    - column: BookingType 
The table should have the title "PriceItems" und the data must be loaded from the server with the following relative URL: 
    "/MembershipTypeService/priceitem/pricelist/{id}"