Prompt for the OperatorApp

Please create a React-JS application for the OperatorModule. The application  has to offer the following views for the user interface: 
    1. CrewedMissionView 
    2. OperatorView 
    3. SpaceportLaunchVehicleUsageView 
    4. SpaceportOperatorView 
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 CrewedMissionView must contain the following fields: 
    - name: CrewedProgram   type: CrewedProgram 
    - name: Destination   type: STRING 
    - name: Launch   type: Launch 
    - name: Notes   type: STRING 
    - name: SpacecraftName   type: STRING 
The data source for the [CrewedProgram] select control should be loaded from the relative URL: 
    "/CountryService/crewedprogram"   (HTTP-GET) 
The data source for the [Launch] select control should be loaded from the relative URL: 
    "/LaunchVehicleService/launch"   (HTTP-GET) 
An existing CrewedMission entity should be loaded from the relative URL: 
    "/OperatorService/crewedmission/{id}"   (HTTP-GET) 
If a new CrewedMission entity has been created, the new entity should be posted to the relative URL: 
    "/OperatorService/crewedmission"   (HTTP-POST) 
If an existing CrewedMission entity has been updated, the modified entity should be sent to the relative URL: 
    "/OperatorService/crewedmission/{id}"   (HTTP-PUT) 
If an existing CrewedMission entity has to be deleted, the following relative URL should be called: 
    "/OperatorService/crewedmission/{id}"   (HTTP-DELETE)

2. The OperatorView must contain the following fields: 
    - name: Country   type: Country 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
    - name: Type   type: STRING 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/CountryService/country"   (HTTP-GET) 
An existing Operator entity should be loaded from the relative URL: 
    "/OperatorService/operator/{id}"   (HTTP-GET) 
If a new Operator entity has been created, the new entity should be posted to the relative URL: 
    "/OperatorService/operator"   (HTTP-POST) 
If an existing Operator entity has been updated, the modified entity should be sent to the relative URL: 
    "/OperatorService/operator/{id}"   (HTTP-PUT) 
If an existing Operator entity has to be deleted, the following relative URL should be called: 
    "/OperatorService/operator/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following LaunchVehicle columns: 
    - column: IsCrewedCapable 
    - column: Type 
    - column: Notes 
    - column: Country 
    - column: Operator 
    - column: Name 
The table should have the title "LaunchVehicles" und the data must be loaded from the server with the following relative URL: 
    "/LaunchVehicleService/launchvehicle/operator/{id}" 
Add a HTML table to the view with the following SpaceportOperator columns: 
    - column: Spaceport 
    - column: Operator 
    - column: ToDate 
    - column: Role 
    - column: FromDate 
The table should have the title "SpaceportOperators" und the data must be loaded from the server with the following relative URL: 
    "/OperatorService/spaceportoperator/operator/{id}"

3. The SpaceportLaunchVehicleUsageView must contain the following fields: 
    - name: FromDate   type: DATE 
    - name: IsPlanned   type: BOOL 
    - name: LaunchVehicle   type: LaunchVehicle 
    - name: Notes   type: STRING 
    - name: Spaceport   type: Spaceport 
    - name: ToDate   type: DATE 
The data source for the [Spaceport] select control should be loaded from the relative URL: 
    "/SpaceportService/spaceport"   (HTTP-GET) 
The data source for the [LaunchVehicle] select control should be loaded from the relative URL: 
    "/LaunchVehicleService/launchvehicle"   (HTTP-GET) 
An existing SpaceportLaunchVehicleUsage entity should be loaded from the relative URL: 
    "/OperatorService/spaceportlaunchvehicleusage/{id}"   (HTTP-GET) 
If a new SpaceportLaunchVehicleUsage entity has been created, the new entity should be posted to the relative URL: 
    "/OperatorService/spaceportlaunchvehicleusage"   (HTTP-POST) 
If an existing SpaceportLaunchVehicleUsage entity has been updated, the modified entity should be sent to the relative URL: 
    "/OperatorService/spaceportlaunchvehicleusage/{id}"   (HTTP-PUT) 
If an existing SpaceportLaunchVehicleUsage entity has to be deleted, the following relative URL should be called: 
    "/OperatorService/spaceportlaunchvehicleusage/{id}"   (HTTP-DELETE)

4. The SpaceportOperatorView must contain the following fields: 
    - name: FromDate   type: DATE 
    - name: Operator   type: Operator 
    - name: Role   type: STRING 
    - name: Spaceport   type: Spaceport 
    - name: ToDate   type: DATE 
The data source for the [Operator] select control should be loaded from the relative URL: 
    "/OperatorService/operator"   (HTTP-GET) 
The data source for the [Spaceport] select control should be loaded from the relative URL: 
    "/SpaceportService/spaceport"   (HTTP-GET) 
An existing SpaceportOperator entity should be loaded from the relative URL: 
    "/OperatorService/spaceportoperator/{id}"   (HTTP-GET) 
If a new SpaceportOperator entity has been created, the new entity should be posted to the relative URL: 
    "/OperatorService/spaceportoperator"   (HTTP-POST) 
If an existing SpaceportOperator entity has been updated, the modified entity should be sent to the relative URL: 
    "/OperatorService/spaceportoperator/{id}"   (HTTP-PUT) 
If an existing SpaceportOperator entity has to be deleted, the following relative URL should be called: 
    "/OperatorService/spaceportoperator/{id}"   (HTTP-DELETE)