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. DownloadLicenseView 
    2. SeasonView 
    3. SubscriptionView 
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 DownloadLicenseView must contain the following fields: 
    - name: DeviceLimit   type: LONG 
    - name: Episode   type: Episode 
    - name: ExpiresAt   type: STRING 
    - name: GrantedAt   type: STRING 
    - name: IsExpired   type: BOOL 
    - name: Profile   type: Profile 
    - name: Season   type: Season 
    - name: Title   type: Title 
The data source for the [Episode] select control should be loaded from the relative URL: 
    "/EpisodeService/episode"   (HTTP-GET) 
The data source for the [Title] select control should be loaded from the relative URL: 
    "/TitleService/title"   (HTTP-GET) 
The data source for the [Season] select control should be loaded from the relative URL: 
    "/SeasonService/season"   (HTTP-GET) 
The data source for the [Profile] select control should be loaded from the relative URL: 
    "/ProfileService/profile"   (HTTP-GET) 
An existing DownloadLicense entity should be loaded from the relative URL: 
    "/SeasonService/downloadlicense/{id}"   (HTTP-GET) 
If a new DownloadLicense entity has been created, the new entity should be posted to the relative URL: 
    "/SeasonService/downloadlicense"   (HTTP-POST) 
If an existing DownloadLicense entity has been updated, the modified entity should be sent to the relative URL: 
    "/SeasonService/downloadlicense/{id}"   (HTTP-PUT) 
If an existing DownloadLicense entity has to be deleted, the following relative URL should be called: 
    "/SeasonService/downloadlicense/{id}"   (HTTP-DELETE)

2. The SeasonView must contain the following fields: 
    - name: Name   type: STRING 
    - name: ReleaseDate   type: DATE 
    - name: SeasonNumber   type: LONG 
    - name: Synopsis   type: STRING 
    - name: Title   type: Title 
The data source for the [Title] select control should be loaded from the relative URL: 
    "/TitleService/title"   (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: Name 
    - column: EpisodeNumber 
    - column: Synopsis 
    - column: RuntimeMinutes 
    - column: Season 
    - column: Title 
    - column: ReleaseDate 
The table should have the title "Episodes" und the data must be loaded from the server with the following relative URL: 
    "/EpisodeService/episode/season/{id}" 
Add a HTML table to the view with the following WatchHistory columns: 
    - column: Episode 
    - column: Profile 
    - column: StartedAt 
    - column: ProgressPercent 
    - column: Season 
    - column: CompletedAt 
    - column: Title 
    - column: LastPositionSeconds 
The table should have the title "WatchHistorys" und the data must be loaded from the server with the following relative URL: 
    "/ProfileService/watchhistory/season/{id}" 
Add a HTML table to the view with the following PlaybackSession columns: 
    - column: IsLive 
    - column: Season 
    - column: Title 
    - column: Profile 
    - column: Episode 
    - column: EndedAt 
    - column: PlaybackType 
    - column: Device 
    - column: StartedAt 
The table should have the title "PlaybackSessions" und the data must be loaded from the server with the following relative URL: 
    "/EpisodeService/playbacksession/season/{id}" 
Add a HTML table to the view with the following DownloadLicense columns: 
    - column: Episode 
    - column: Profile 
    - column: Season 
    - column: DeviceLimit 
    - column: GrantedAt 
    - column: IsExpired 
    - column: ExpiresAt 
    - column: Title 
The table should have the title "DownloadLicenses" und the data must be loaded from the server with the following relative URL: 
    "/SeasonService/downloadlicense/season/{id}"

3. The SubscriptionView must contain the following fields: 
    - name: AutoRenew   type: BOOL 
    - name: EndDate   type: DATE 
    - name: StartDate   type: DATE 
    - name: Status   type: STRING 
    - name: SubscriptionPlan   type: SubscriptionPlan 
    - name: User   type: User 
The data source for the [SubscriptionPlan] select control should be loaded from the relative URL: 
    "/SubscriptionPlanService/subscriptionplan"   (HTTP-GET) 
The data source for the [User] select control should be loaded from the relative URL: 
    "/UserService/user"   (HTTP-GET) 
An existing Subscription entity should be loaded from the relative URL: 
    "/SeasonService/subscription/{id}"   (HTTP-GET) 
If a new Subscription entity has been created, the new entity should be posted to the relative URL: 
    "/SeasonService/subscription"   (HTTP-POST) 
If an existing Subscription entity has been updated, the modified entity should be sent to the relative URL: 
    "/SeasonService/subscription/{id}"   (HTTP-PUT) 
If an existing Subscription entity has to be deleted, the following relative URL should be called: 
    "/SeasonService/subscription/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Payment columns: 
    - column: Status 
    - column: Amount 
    - column: PaidAt 
    - column: Currency 
    - column: User 
    - column: Subscription 
    - column: Description 
    - column: PaymentMethod 
The table should have the title "Payments" und the data must be loaded from the server with the following relative URL: 
    "/UserService/payment/subscription/{id}"