Prompt for the VehicleModelApp

Please create a React-JS application for the VehicleModelModule. The application  has to offer the following views for the user interface: 
    1. ProjectView 
    2. RecallView 
    3. VehicleBatteryOptionView 
    4. VehicleCategoryView 
    5. VehicleModelView 
    6. VehicleSalesStatView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 6 views are defined below.

1. The ProjectView must contain the following fields: 
    - name: AnnouncementDate   type: DATE 
    - name: Company   type: Company 
    - name: Description   type: STRING 
    - name: PlannedEndYear   type: INT 
    - name: PlannedStartYear   type: INT 
    - name: ProjectName   type: STRING 
    - name: ProjectType   type: STRING 
    - name: RelatedVehicleModel   type: VehicleModel 
    - name: Status   type: STRING 
The data source for the [Company] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
The data source for the [RelatedVehicleModel] select control should be loaded from the relative URL: 
    "/VehicleModelService/vehiclemodel"   (HTTP-GET) 
An existing Project entity should be loaded from the relative URL: 
    "/VehicleModelService/project/{id}"   (HTTP-GET) 
If a new Project entity has been created, the new entity should be posted to the relative URL: 
    "/VehicleModelService/project"   (HTTP-POST) 
If an existing Project entity has been updated, the modified entity should be sent to the relative URL: 
    "/VehicleModelService/project/{id}"   (HTTP-PUT) 
If an existing Project entity has to be deleted, the following relative URL should be called: 
    "/VehicleModelService/project/{id}"   (HTTP-DELETE)

2. The RecallView must contain the following fields: 
    - name: AffectedUnits   type: INT 
    - name: AnnouncementDate   type: DATE 
    - name: IssueDescription   type: STRING 
    - name: MarketRegion   type: STRING 
    - name: RecallCode   type: STRING 
    - name: VehicleModel   type: VehicleModel 
The data source for the [VehicleModel] select control should be loaded from the relative URL: 
    "/VehicleModelService/vehiclemodel"   (HTTP-GET) 
An existing Recall entity should be loaded from the relative URL: 
    "/VehicleModelService/recall/{id}"   (HTTP-GET) 
If a new Recall entity has been created, the new entity should be posted to the relative URL: 
    "/VehicleModelService/recall"   (HTTP-POST) 
If an existing Recall entity has been updated, the modified entity should be sent to the relative URL: 
    "/VehicleModelService/recall/{id}"   (HTTP-PUT) 
If an existing Recall entity has to be deleted, the following relative URL should be called: 
    "/VehicleModelService/recall/{id}"   (HTTP-DELETE)

3. The VehicleBatteryOptionView must contain the following fields: 
    - name: BatteryPack   type: BatteryPack 
    - name: EndYear   type: INT 
    - name: IsPerformanceVariant   type: BOOL 
    - name: OptionName   type: STRING 
    - name: RangeKm   type: INT 
    - name: StartYear   type: INT 
    - name: VehicleModel   type: VehicleModel 
The data source for the [VehicleModel] select control should be loaded from the relative URL: 
    "/VehicleModelService/vehiclemodel"   (HTTP-GET) 
The data source for the [BatteryPack] select control should be loaded from the relative URL: 
    "/BatteryPackService/batterypack"   (HTTP-GET) 
An existing VehicleBatteryOption entity should be loaded from the relative URL: 
    "/VehicleModelService/vehiclebatteryoption/{id}"   (HTTP-GET) 
If a new VehicleBatteryOption entity has been created, the new entity should be posted to the relative URL: 
    "/VehicleModelService/vehiclebatteryoption"   (HTTP-POST) 
If an existing VehicleBatteryOption entity has been updated, the modified entity should be sent to the relative URL: 
    "/VehicleModelService/vehiclebatteryoption/{id}"   (HTTP-PUT) 
If an existing VehicleBatteryOption entity has to be deleted, the following relative URL should be called: 
    "/VehicleModelService/vehiclebatteryoption/{id}"   (HTTP-DELETE)

4. The VehicleCategoryView must contain the following fields: 
    - name: CategoryName   type: STRING 
    - name: Description   type: STRING 
An existing VehicleCategory entity should be loaded from the relative URL: 
    "/VehicleModelService/vehiclecategory/{id}"   (HTTP-GET) 
If a new VehicleCategory entity has been created, the new entity should be posted to the relative URL: 
    "/VehicleModelService/vehiclecategory"   (HTTP-POST) 
If an existing VehicleCategory entity has been updated, the modified entity should be sent to the relative URL: 
    "/VehicleModelService/vehiclecategory/{id}"   (HTTP-PUT) 
If an existing VehicleCategory entity has to be deleted, the following relative URL should be called: 
    "/VehicleModelService/vehiclecategory/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following VehicleModel columns: 
    - column: ModelName 
    - column: Notes 
    - column: InitialRevealDate 
    - column: GenerationName 
    - column: BasePriceUsd 
    - column: MarketSegment 
    - column: ProductionStartYear 
    - column: ProductionEndYear 
    - column: Product 
    - column: VehicleCategory 
The table should have the title "VehicleModels" und the data must be loaded from the server with the following relative URL: 
    "/VehicleModelService/vehiclemodel/vehiclecategory/{id}"

5. The VehicleModelView must contain the following fields: 
    - name: BasePriceUsd   type: DOUBLE 
    - name: GenerationName   type: STRING 
    - name: InitialRevealDate   type: DATE 
    - name: MarketSegment   type: STRING 
    - name: ModelName   type: STRING 
    - name: Notes   type: STRING 
    - name: Product   type: Product 
    - name: ProductionEndYear   type: INT 
    - name: ProductionStartYear   type: INT 
    - name: VehicleCategory   type: VehicleCategory 
The data source for the [Product] select control should be loaded from the relative URL: 
    "/CompanyService/product"   (HTTP-GET) 
The data source for the [VehicleCategory] select control should be loaded from the relative URL: 
    "/VehicleModelService/vehiclecategory"   (HTTP-GET) 
An existing VehicleModel entity should be loaded from the relative URL: 
    "/VehicleModelService/vehiclemodel/{id}"   (HTTP-GET) 
If a new VehicleModel entity has been created, the new entity should be posted to the relative URL: 
    "/VehicleModelService/vehiclemodel"   (HTTP-POST) 
If an existing VehicleModel entity has been updated, the modified entity should be sent to the relative URL: 
    "/VehicleModelService/vehiclemodel/{id}"   (HTTP-PUT) 
If an existing VehicleModel entity has to be deleted, the following relative URL should be called: 
    "/VehicleModelService/vehiclemodel/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Recall columns: 
    - column: AnnouncementDate 
    - column: VehicleModel 
    - column: AffectedUnits 
    - column: RecallCode 
    - column: MarketRegion 
    - column: IssueDescription 
The table should have the title "Recalls" und the data must be loaded from the server with the following relative URL: 
    "/VehicleModelService/recall/vehiclemodel/{id}" 
Add a HTML table to the view with the following VehicleSalesStat columns: 
    - column: MarketRegion 
    - column: UnitsSold 
    - column: CalendarYear 
    - column: Note 
    - column: VehicleModel 
    - column: IsGlobal 
The table should have the title "VehicleSalesStats" und the data must be loaded from the server with the following relative URL: 
    "/VehicleModelService/vehiclesalesstat/vehiclemodel/{id}" 
Add a HTML table to the view with the following VehicleBatteryOption columns: 
    - column: VehicleModel 
    - column: EndYear 
    - column: StartYear 
    - column: IsPerformanceVariant 
    - column: RangeKm 
    - column: OptionName 
    - column: BatteryPack 
The table should have the title "VehicleBatteryOptions" und the data must be loaded from the server with the following relative URL: 
    "/VehicleModelService/vehiclebatteryoption/vehiclemodel/{id}" 
Add a HTML table to the view with the following Project columns: 
    - column: ProjectName 
    - column: RelatedVehicleModel 
    - column: PlannedEndYear 
    - column: PlannedStartYear 
    - column: Description 
    - column: AnnouncementDate 
    - column: ProjectType 
    - column: Company 
    - column: Status 
The table should have the title "Projects" und the data must be loaded from the server with the following relative URL: 
    "/VehicleModelService/project/relatedvehiclemodel/{id}" 
Add a HTML table to the view with the following VehicleSpecification columns: 
    - column: ZeroToHundredKmhSeconds 
    - column: SpecVersionName 
    - column: StartYear 
    - column: LengthMm 
    - column: RangeKm 
    - column: HeightMm 
    - column: Seats 
    - column: CurbWeightKg 
    - column: MarketRegion 
    - column: TopSpeedKmh 
    - column: WidthMm 
    - column: DriveType 
    - column: BatteryWeightKg 
    - column: VehicleModel 
    - column: EndYear 
The table should have the title "VehicleSpecifications" und the data must be loaded from the server with the following relative URL: 
    "/CityService/vehiclespecification/vehiclemodel/{id}"

6. The VehicleSalesStatView must contain the following fields: 
    - name: CalendarYear   type: INT 
    - name: IsGlobal   type: BOOL 
    - name: MarketRegion   type: STRING 
    - name: Note   type: STRING 
    - name: UnitsSold   type: INT 
    - name: VehicleModel   type: VehicleModel 
The data source for the [VehicleModel] select control should be loaded from the relative URL: 
    "/VehicleModelService/vehiclemodel"   (HTTP-GET) 
An existing VehicleSalesStat entity should be loaded from the relative URL: 
    "/VehicleModelService/vehiclesalesstat/{id}"   (HTTP-GET) 
If a new VehicleSalesStat entity has been created, the new entity should be posted to the relative URL: 
    "/VehicleModelService/vehiclesalesstat"   (HTTP-POST) 
If an existing VehicleSalesStat entity has been updated, the modified entity should be sent to the relative URL: 
    "/VehicleModelService/vehiclesalesstat/{id}"   (HTTP-PUT) 
If an existing VehicleSalesStat entity has to be deleted, the following relative URL should be called: 
    "/VehicleModelService/vehiclesalesstat/{id}"   (HTTP-DELETE)