Prompt for the SeasonApp

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

1. The EpisodeView must contain the following fields: 
    - name: ContentTitle   type: ContentTitle 
    - name: EpisodeNumber   type: LONG 
    - name: ReleaseDate   type: DATE 
    - name: RuntimeMinutes   type: LONG 
    - name: Season   type: Season 
    - name: Synopsis   type: STRING 
    - name: Title   type: STRING 
The data source for the [Season] select control should be loaded from the relative URL: 
    "/SeasonService/season"   (HTTP-GET) 
The data source for the [ContentTitle] select control should be loaded from the relative URL: 
    "/ContentTitleService/contenttitle"   (HTTP-GET) 
An existing Episode entity should be loaded from the relative URL: 
    "/SeasonService/episode/{id}"   (HTTP-GET) 
If a new Episode entity has been created, the new entity should be posted to the relative URL: 
    "/SeasonService/episode"   (HTTP-POST) 
If an existing Episode entity has been updated, the modified entity should be sent to the relative URL: 
    "/SeasonService/episode/{id}"   (HTTP-PUT) 
If an existing Episode entity has to be deleted, the following relative URL should be called: 
    "/SeasonService/episode/{id}"   (HTTP-DELETE)

2. The SeasonView must contain the following fields: 
    - name: ContentTitle   type: ContentTitle 
    - name: EpisodeCount   type: LONG 
    - name: ReleaseDate   type: DATE 
    - name: SeasonNumber   type: LONG 
The data source for the [ContentTitle] select control should be loaded from the relative URL: 
    "/ContentTitleService/contenttitle"   (HTTP-GET) 
An existing Season entity should be loaded from the relative URL: 
    "/SeasonService/season/{id}"   (HTTP-GET) 
If a new Season entity has been created, the new entity should be posted to the relative URL: 
    "/SeasonService/season"   (HTTP-POST) 
If an existing Season entity has been updated, the modified entity should be sent to the relative URL: 
    "/SeasonService/season/{id}"   (HTTP-PUT) 
If an existing Season entity has to be deleted, the following relative URL should be called: 
    "/SeasonService/season/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Episode columns: 
    - column: Synopsis 
    - column: Title 
    - column: ContentTitle 
    - column: RuntimeMinutes 
    - column: Season 
    - column: EpisodeNumber 
    - column: ReleaseDate 
The table should have the title "Episodes" und the data must be loaded from the server with the following relative URL: 
    "/SeasonService/episode/season/{id}"

3. The ServiceFeatureView must contain the following fields: 
    - name: Description   type: STRING 
    - name: LaunchDate   type: DATE 
    - name: Name   type: STRING 
    - name: ServiceSupply   type: ServiceSupply 
The data source for the [ServiceSupply] select control should be loaded from the relative URL: 
    "/ServiceSupplyService/servicesupply"   (HTTP-GET) 
An existing ServiceFeature entity should be loaded from the relative URL: 
    "/SeasonService/servicefeature/{id}"   (HTTP-GET) 
If a new ServiceFeature entity has been created, the new entity should be posted to the relative URL: 
    "/SeasonService/servicefeature"   (HTTP-POST) 
If an existing ServiceFeature entity has been updated, the modified entity should be sent to the relative URL: 
    "/SeasonService/servicefeature/{id}"   (HTTP-PUT) 
If an existing ServiceFeature entity has to be deleted, the following relative URL should be called: 
    "/SeasonService/servicefeature/{id}"   (HTTP-DELETE)