Prompt for the ChannelApp

Please create a React-JS application for the ChannelModule. The application  has to offer the following views for the user interface: 
    1. ChannelView 
    2. LiveProgramView 
    3. SportsEventView 
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 ChannelView must contain the following fields: 
    - name: Description   type: STRING 
    - name: IsLive   type: BOOL 
    - name: Name   type: STRING 
    - name: ProviderCompany   type: Company 
    - name: Website   type: STRING 
The data source for the [ProviderCompany] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
An existing Channel entity should be loaded from the relative URL: 
    "/ChannelService/channel/{id}"   (HTTP-GET) 
If a new Channel entity has been created, the new entity should be posted to the relative URL: 
    "/ChannelService/channel"   (HTTP-POST) 
If an existing Channel entity has been updated, the modified entity should be sent to the relative URL: 
    "/ChannelService/channel/{id}"   (HTTP-PUT) 
If an existing Channel entity has to be deleted, the following relative URL should be called: 
    "/ChannelService/channel/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following ChannelSubscription columns: 
    - column: StartDate 
    - column: Channel 
    - column: User 
    - column: EndDate 
    - column: AutoRenew 
    - column: Status 
The table should have the title "ChannelSubscriptions" und the data must be loaded from the server with the following relative URL: 
    "/DrmSchemeService/channelsubscription/channel/{id}" 
Add a HTML table to the view with the following LiveProgram columns: 
    - column: IsSportsEvent 
    - column: Channel 
    - column: EndTime 
    - column: Title 
    - column: SportsEvent 
    - column: StartTime 
The table should have the title "LivePrograms" und the data must be loaded from the server with the following relative URL: 
    "/ChannelService/liveprogram/channel/{id}"

2. The LiveProgramView must contain the following fields: 
    - name: Channel   type: Channel 
    - name: EndTime   type: STRING 
    - name: IsSportsEvent   type: BOOL 
    - name: SportsEvent   type: SportsEvent 
    - name: StartTime   type: STRING 
    - name: Title   type: Title 
The data source for the [SportsEvent] select control should be loaded from the relative URL: 
    "/ChannelService/sportsevent"   (HTTP-GET) 
The data source for the [Channel] select control should be loaded from the relative URL: 
    "/ChannelService/channel"   (HTTP-GET) 
The data source for the [Title] select control should be loaded from the relative URL: 
    "/TitleService/title"   (HTTP-GET) 
An existing LiveProgram entity should be loaded from the relative URL: 
    "/ChannelService/liveprogram/{id}"   (HTTP-GET) 
If a new LiveProgram entity has been created, the new entity should be posted to the relative URL: 
    "/ChannelService/liveprogram"   (HTTP-POST) 
If an existing LiveProgram entity has been updated, the modified entity should be sent to the relative URL: 
    "/ChannelService/liveprogram/{id}"   (HTTP-PUT) 
If an existing LiveProgram entity has to be deleted, the following relative URL should be called: 
    "/ChannelService/liveprogram/{id}"   (HTTP-DELETE)

3. The SportsEventView must contain the following fields: 
    - name: CompetitionName   type: STRING 
    - name: Country   type: Country 
    - name: EventDate   type: STRING 
    - name: Name   type: STRING 
    - name: SportType   type: STRING 
    - name: Title   type: Title 
    - name: Venue   type: STRING 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/TitleService/country"   (HTTP-GET) 
The data source for the [Title] select control should be loaded from the relative URL: 
    "/TitleService/title"   (HTTP-GET) 
An existing SportsEvent entity should be loaded from the relative URL: 
    "/ChannelService/sportsevent/{id}"   (HTTP-GET) 
If a new SportsEvent entity has been created, the new entity should be posted to the relative URL: 
    "/ChannelService/sportsevent"   (HTTP-POST) 
If an existing SportsEvent entity has been updated, the modified entity should be sent to the relative URL: 
    "/ChannelService/sportsevent/{id}"   (HTTP-PUT) 
If an existing SportsEvent entity has to be deleted, the following relative URL should be called: 
    "/ChannelService/sportsevent/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following LiveProgram columns: 
    - column: IsSportsEvent 
    - column: Channel 
    - column: EndTime 
    - column: Title 
    - column: SportsEvent 
    - column: StartTime 
The table should have the title "LivePrograms" und the data must be loaded from the server with the following relative URL: 
    "/ChannelService/liveprogram/sportsevent/{id}"