Prompt for the LoyaltyAccountApp

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

1. The LoyaltyAccountView must contain the following fields: 
    - name: AccountNumber   type: STRING 
    - name: EnrollDate   type: DATE 
    - name: LoyaltyProgram   type: LoyaltyProgram 
    - name: Passenger   type: Passenger 
    - name: Status   type: STRING 
    - name: Tier   type: LoyaltyTier 
The data source for the [LoyaltyProgram] select control should be loaded from the relative URL: 
    "/LoyaltyProgramService/loyaltyprogram"   (HTTP-GET) 
The data source for the [Tier] select control should be loaded from the relative URL: 
    "/LoyaltyProgramService/loyaltytier"   (HTTP-GET) 
The data source for the [Passenger] select control should be loaded from the relative URL: 
    "/AirlineService/passenger"   (HTTP-GET) 
An existing LoyaltyAccount entity should be loaded from the relative URL: 
    "/LoyaltyAccountService/loyaltyaccount/{id}"   (HTTP-GET) 
If a new LoyaltyAccount entity has been created, the new entity should be posted to the relative URL: 
    "/LoyaltyAccountService/loyaltyaccount"   (HTTP-POST) 
If an existing LoyaltyAccount entity has been updated, the modified entity should be sent to the relative URL: 
    "/LoyaltyAccountService/loyaltyaccount/{id}"   (HTTP-PUT) 
If an existing LoyaltyAccount entity has to be deleted, the following relative URL should be called: 
    "/LoyaltyAccountService/loyaltyaccount/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following LoyaltyTransaction columns: 
    - column: LoyaltyAccount 
    - column: RelatedFlightInstance 
    - column: Miles 
    - column: TransactionType 
    - column: TransactionDate 
    - column: Description 
The table should have the title "LoyaltyTransactions" und the data must be loaded from the server with the following relative URL: 
    "/LoyaltyAccountService/loyaltytransaction/loyaltyaccount/{id}"

2. The LoyaltyTransactionView must contain the following fields: 
    - name: Description   type: STRING 
    - name: LoyaltyAccount   type: LoyaltyAccount 
    - name: Miles   type: LONG 
    - name: RelatedFlightInstance   type: FlightInstance 
    - name: TransactionDate   type: STRING 
    - name: TransactionType   type: STRING 
The data source for the [RelatedFlightInstance] select control should be loaded from the relative URL: 
    "/FlightInstanceService/flightinstance"   (HTTP-GET) 
The data source for the [LoyaltyAccount] select control should be loaded from the relative URL: 
    "/LoyaltyAccountService/loyaltyaccount"   (HTTP-GET) 
An existing LoyaltyTransaction entity should be loaded from the relative URL: 
    "/LoyaltyAccountService/loyaltytransaction/{id}"   (HTTP-GET) 
If a new LoyaltyTransaction entity has been created, the new entity should be posted to the relative URL: 
    "/LoyaltyAccountService/loyaltytransaction"   (HTTP-POST) 
If an existing LoyaltyTransaction entity has been updated, the modified entity should be sent to the relative URL: 
    "/LoyaltyAccountService/loyaltytransaction/{id}"   (HTTP-PUT) 
If an existing LoyaltyTransaction entity has to be deleted, the following relative URL should be called: 
    "/LoyaltyAccountService/loyaltytransaction/{id}"   (HTTP-DELETE)

Overview