Prompt for the FlightNumberApp

Please create a React-JS application for the FlightNumberModule. The application  has to offer the following views for the user interface: 
    1. CodeshareAgreementView 
    2. FlightNumberView 
    3. FlightScheduleView 
    4. RouteView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below.

1. The CodeshareAgreementView must contain the following fields: 
    - name: EndDate   type: DATE 
    - name: FlightNumber   type: FlightNumber 
    - name: MarketingAirline   type: Airline 
    - name: Notes   type: STRING 
    - name: OperatingAirline   type: Airline 
    - name: StartDate   type: DATE 
The data source for the [MarketingAirline] select control should be loaded from the relative URL: 
    "/AirlineService/airline"   (HTTP-GET) 
The data source for the [FlightNumber] select control should be loaded from the relative URL: 
    "/FlightNumberService/flightnumber"   (HTTP-GET) 
The data source for the [OperatingAirline] select control should be loaded from the relative URL: 
    "/AirlineService/airline"   (HTTP-GET) 
An existing CodeshareAgreement entity should be loaded from the relative URL: 
    "/FlightNumberService/codeshareagreement/{id}"   (HTTP-GET) 
If a new CodeshareAgreement entity has been created, the new entity should be posted to the relative URL: 
    "/FlightNumberService/codeshareagreement"   (HTTP-POST) 
If an existing CodeshareAgreement entity has been updated, the modified entity should be sent to the relative URL: 
    "/FlightNumberService/codeshareagreement/{id}"   (HTTP-PUT) 
If an existing CodeshareAgreement entity has to be deleted, the following relative URL should be called: 
    "/FlightNumberService/codeshareagreement/{id}"   (HTTP-DELETE)

2. The FlightNumberView must contain the following fields: 
    - name: Airline   type: Airline 
    - name: Code   type: STRING 
    - name: Description   type: STRING 
The data source for the [Airline] select control should be loaded from the relative URL: 
    "/AirlineService/airline"   (HTTP-GET) 
An existing FlightNumber entity should be loaded from the relative URL: 
    "/FlightNumberService/flightnumber/{id}"   (HTTP-GET) 
If a new FlightNumber entity has been created, the new entity should be posted to the relative URL: 
    "/FlightNumberService/flightnumber"   (HTTP-POST) 
If an existing FlightNumber entity has been updated, the modified entity should be sent to the relative URL: 
    "/FlightNumberService/flightnumber/{id}"   (HTTP-PUT) 
If an existing FlightNumber entity has to be deleted, the following relative URL should be called: 
    "/FlightNumberService/flightnumber/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following FlightSchedule columns: 
    - column: OperatingDaysMask 
    - column: EffectiveTo 
    - column: EffectiveFrom 
    - column: DepartureTimeLocal 
    - column: Route 
    - column: ArrivalTimeLocal 
    - column: FlightNumber 
    - column: AircraftModel 
The table should have the title "FlightSchedules" und the data must be loaded from the server with the following relative URL: 
    "/FlightNumberService/flightschedule/flightnumber/{id}" 
Add a HTML table to the view with the following CodeshareAgreement columns: 
    - column: OperatingAirline 
    - column: StartDate 
    - column: Notes 
    - column: FlightNumber 
    - column: MarketingAirline 
    - column: EndDate 
The table should have the title "CodeshareAgreements" und the data must be loaded from the server with the following relative URL: 
    "/FlightNumberService/codeshareagreement/flightnumber/{id}"

3. The FlightScheduleView must contain the following fields: 
    - name: AircraftModel   type: AircraftModel 
    - name: ArrivalTimeLocal   type: STRING 
    - name: DepartureTimeLocal   type: STRING 
    - name: EffectiveFrom   type: DATE 
    - name: EffectiveTo   type: DATE 
    - name: FlightNumber   type: FlightNumber 
    - name: OperatingDaysMask   type: LONG 
    - name: Route   type: Route 
The data source for the [FlightNumber] select control should be loaded from the relative URL: 
    "/FlightNumberService/flightnumber"   (HTTP-GET) 
The data source for the [AircraftModel] select control should be loaded from the relative URL: 
    "/AircraftModelService/aircraftmodel"   (HTTP-GET) 
The data source for the [Route] select control should be loaded from the relative URL: 
    "/FlightNumberService/route"   (HTTP-GET) 
An existing FlightSchedule entity should be loaded from the relative URL: 
    "/FlightNumberService/flightschedule/{id}"   (HTTP-GET) 
If a new FlightSchedule entity has been created, the new entity should be posted to the relative URL: 
    "/FlightNumberService/flightschedule"   (HTTP-POST) 
If an existing FlightSchedule entity has been updated, the modified entity should be sent to the relative URL: 
    "/FlightNumberService/flightschedule/{id}"   (HTTP-PUT) 
If an existing FlightSchedule entity has to be deleted, the following relative URL should be called: 
    "/FlightNumberService/flightschedule/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following FlightInstance columns: 
    - column: ScheduledDepartureUtc 
    - column: ScheduledArrivalUtc 
    - column: Status 
    - column: FlightSchedule 
    - column: ActualDepartureUtc 
    - column: ActualArrivalUtc 
    - column: Aircraft 
The table should have the title "FlightInstances" und the data must be loaded from the server with the following relative URL: 
    "/FlightInstanceService/flightinstance/flightschedule/{id}"

4. The RouteView must contain the following fields: 
    - name: ActiveFrom   type: DATE 
    - name: ActiveTo   type: DATE 
    - name: Airline   type: Airline 
    - name: DestinationAirport   type: Airport 
    - name: DistanceKm   type: LONG 
    - name: DomesticInternational   type: STRING 
    - name: OriginAirport   type: Airport 
The data source for the [OriginAirport] select control should be loaded from the relative URL: 
    "/AirportService/airport"   (HTTP-GET) 
The data source for the [Airline] select control should be loaded from the relative URL: 
    "/AirlineService/airline"   (HTTP-GET) 
The data source for the [DestinationAirport] select control should be loaded from the relative URL: 
    "/AirportService/airport"   (HTTP-GET) 
An existing Route entity should be loaded from the relative URL: 
    "/FlightNumberService/route/{id}"   (HTTP-GET) 
If a new Route entity has been created, the new entity should be posted to the relative URL: 
    "/FlightNumberService/route"   (HTTP-POST) 
If an existing Route entity has been updated, the modified entity should be sent to the relative URL: 
    "/FlightNumberService/route/{id}"   (HTTP-PUT) 
If an existing Route entity has to be deleted, the following relative URL should be called: 
    "/FlightNumberService/route/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following FlightSchedule columns: 
    - column: OperatingDaysMask 
    - column: EffectiveTo 
    - column: EffectiveFrom 
    - column: DepartureTimeLocal 
    - column: Route 
    - column: ArrivalTimeLocal 
    - column: FlightNumber 
    - column: AircraftModel 
The table should have the title "FlightSchedules" und the data must be loaded from the server with the following relative URL: 
    "/FlightNumberService/flightschedule/route/{id}"