Prompt for the UserAccountApp

Please create a React-JS application for the UserAccountModule. The application  has to offer the following views for the user interface: 
    1. LoyaltyProgramView 
    2. PaymentMethodView 
    3. TravelCreditTransactionView 
    4. UserAccountView 
    5. UserLoyaltyStatusView 
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 LoyaltyProgramView must contain the following fields: 
    - name: Code   type: STRING 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
An existing LoyaltyProgram entity should be loaded from the relative URL: 
    "/UserAccountService/loyaltyprogram/{id}"   (HTTP-GET) 
If a new LoyaltyProgram entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/loyaltyprogram"   (HTTP-POST) 
If an existing LoyaltyProgram entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/loyaltyprogram/{id}"   (HTTP-PUT) 
If an existing LoyaltyProgram entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/loyaltyprogram/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following UserLoyaltyStatus columns: 
    - column: UserAccount 
    - column: LoyaltyProgram 
    - column: LevelCode 
    - column: EarnedAt 
    - column: ExpiresAt 
    - column: LevelName 
The table should have the title "UserLoyaltyStatuss" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/userloyaltystatus/loyaltyprogram/{id}"

2. The PaymentMethodView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: ExpiryMonth   type: INT 
    - name: ExpiryYear   type: INT 
    - name: HolderName   type: STRING 
    - name: IsActive   type: BOOL 
    - name: IsDefault   type: BOOL 
    - name: MaskedDetails   type: STRING 
    - name: Type   type: STRING 
    - name: UserAccount   type: UserAccount 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing PaymentMethod entity should be loaded from the relative URL: 
    "/UserAccountService/paymentmethod/{id}"   (HTTP-GET) 
If a new PaymentMethod entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/paymentmethod"   (HTTP-POST) 
If an existing PaymentMethod entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/paymentmethod/{id}"   (HTTP-PUT) 
If an existing PaymentMethod entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/paymentmethod/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Payment columns: 
    - column: Currency 
    - column: Booking 
    - column: Status 
    - column: ProviderReference 
    - column: Amount 
    - column: ProcessedAt 
    - column: CreatedAt 
    - column: PaymentMethod 
The table should have the title "Payments" und the data must be loaded from the server with the following relative URL: 
    "/CurrencyService/payment/paymentmethod/{id}"

3. The TravelCreditTransactionView must contain the following fields: 
    - name: Amount   type: STRING 
    - name: Booking   type: INT 
    - name: CreatedAt   type: DATE 
    - name: Currency   type: Currency 
    - name: Description   type: STRING 
    - name: Type   type: STRING 
    - name: UserAccount   type: UserAccount 
The data source for the [Currency] select control should be loaded from the relative URL: 
    "/CurrencyService/currency"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing TravelCreditTransaction entity should be loaded from the relative URL: 
    "/UserAccountService/travelcredittransaction/{id}"   (HTTP-GET) 
If a new TravelCreditTransaction entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/travelcredittransaction"   (HTTP-POST) 
If an existing TravelCreditTransaction entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/travelcredittransaction/{id}"   (HTTP-PUT) 
If an existing TravelCreditTransaction entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/travelcredittransaction/{id}"   (HTTP-DELETE)

4. The UserAccountView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: DefaultCurrency   type: Currency 
    - name: DefaultLanguage   type: Language 
    - name: Email   type: STRING 
    - name: FullName   type: STRING 
    - name: IsActive   type: BOOL 
    - name: PasswordHash   type: STRING 
    - name: PhoneNumber   type: STRING 
The data source for the [DefaultLanguage] select control should be loaded from the relative URL: 
    "/LanguageService/language"   (HTTP-GET) 
The data source for the [DefaultCurrency] select control should be loaded from the relative URL: 
    "/CurrencyService/currency"   (HTTP-GET) 
An existing UserAccount entity should be loaded from the relative URL: 
    "/UserAccountService/useraccount/{id}"   (HTTP-GET) 
If a new UserAccount entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-POST) 
If an existing UserAccount entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/useraccount/{id}"   (HTTP-PUT) 
If an existing UserAccount entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/useraccount/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following UserLoyaltyStatus columns: 
    - column: UserAccount 
    - column: LoyaltyProgram 
    - column: LevelCode 
    - column: EarnedAt 
    - column: ExpiresAt 
    - column: LevelName 
The table should have the title "UserLoyaltyStatuss" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/userloyaltystatus/useraccount/{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/useraccount/{id}" 
Add a HTML table to the view with the following TravelCreditTransaction columns: 
    - column: UserAccount 
    - column: Amount 
    - column: CreatedAt 
    - column: Booking 
    - column: Description 
    - column: Currency 
    - column: Type 
The table should have the title "TravelCreditTransactions" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/travelcredittransaction/useraccount/{id}" 
Add a HTML table to the view with the following PaymentMethod columns: 
    - column: MaskedDetails 
    - column: IsActive 
    - column: IsDefault 
    - column: Type 
    - column: ExpiryYear 
    - column: HolderName 
    - column: UserAccount 
    - column: ExpiryMonth 
    - column: CreatedAt 
The table should have the title "PaymentMethods" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/paymentmethod/useraccount/{id}" 
Add a HTML table to the view with the following Booking columns: 
    - column: Channel 
    - column: UserAccount 
    - column: Currency 
    - column: UpdatedAt 
    - column: Status 
    - column: TotalAmount 
    - column: DisplayAmount 
    - column: CreatedAt 
The table should have the title "Bookings" und the data must be loaded from the server with the following relative URL: 
    "/BookingService/booking/useraccount/{id}"

5. The UserLoyaltyStatusView must contain the following fields: 
    - name: EarnedAt   type: DATE 
    - name: ExpiresAt   type: DATE 
    - name: LevelCode   type: STRING 
    - name: LevelName   type: STRING 
    - name: LoyaltyProgram   type: LoyaltyProgram 
    - name: UserAccount   type: UserAccount 
The data source for the [LoyaltyProgram] select control should be loaded from the relative URL: 
    "/UserAccountService/loyaltyprogram"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing UserLoyaltyStatus entity should be loaded from the relative URL: 
    "/UserAccountService/userloyaltystatus/{id}"   (HTTP-GET) 
If a new UserLoyaltyStatus entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/userloyaltystatus"   (HTTP-POST) 
If an existing UserLoyaltyStatus entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/userloyaltystatus/{id}"   (HTTP-PUT) 
If an existing UserLoyaltyStatus entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/userloyaltystatus/{id}"   (HTTP-DELETE)