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. AudienceMetricView 
    2. ChannelView 
    3. ChannelSettingView 
    4. SubscriptionView 
    5. UserFeedItemView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 5 views are defined below.

1. The AudienceMetricView must contain the following fields: 
    - name: AgeGroup   type: STRING 
    - name: Channel   type: Channel 
    - name: Country   type: STRING 
    - name: Date   type: DATE 
    - name: Gender   type: STRING 
    - name: ViewerCount   type: LONG 
    - name: WatchTimeSeconds   type: LONG 
The data source for the [Channel] select control should be loaded from the relative URL: 
    "/ChannelService/channel"   (HTTP-GET) 
An existing AudienceMetric entity should be loaded from the relative URL: 
    "/ChannelService/audiencemetric/{id}"   (HTTP-GET) 
If a new AudienceMetric entity has been created, the new entity should be posted to the relative URL: 
    "/ChannelService/audiencemetric"   (HTTP-POST) 
If an existing AudienceMetric entity has been updated, the modified entity should be sent to the relative URL: 
    "/ChannelService/audiencemetric/{id}"   (HTTP-PUT) 
If an existing AudienceMetric entity has to be deleted, the following relative URL should be called: 
    "/ChannelService/audiencemetric/{id}"   (HTTP-DELETE)

2. The ChannelView must contain the following fields: 
    - name: AvatarUrl   type: STRING 
    - name: BannerImageUrl   type: STRING 
    - name: Country   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: CustomUrl   type: STRING 
    - name: Description   type: STRING 
    - name: Handle   type: STRING 
    - name: IsVerified   type: BOOL 
    - name: Language   type: STRING 
    - name: Name   type: STRING 
    - name: OwnerUser   type: User 
    - name: Status   type: STRING 
    - name: UpdatedAt   type: DATE 
The data source for the [OwnerUser] select control should be loaded from the relative URL: 
    "/UserService/user"   (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 LiveStream columns: 
    - column: Description 
    - column: Title 
    - column: ActualEndAt 
    - column: Channel 
    - column: CreatedAt 
    - column: Status 
    - column: ConcurrentViewersPeak 
    - column: ScheduledStartAt 
    - column: Video 
    - column: ActualStartAt 
The table should have the title "LiveStreams" und the data must be loaded from the server with the following relative URL: 
    "/LiveStreamService/livestream/channel/{id}" 
Add a HTML table to the view with the following AudienceMetric columns: 
    - column: Channel 
    - column: AgeGroup 
    - column: Country 
    - column: WatchTimeSeconds 
    - column: ViewerCount 
    - column: Date 
    - column: Gender 
The table should have the title "AudienceMetrics" und the data must be loaded from the server with the following relative URL: 
    "/ChannelService/audiencemetric/channel/{id}" 
Add a HTML table to the view with the following ChannelSetting columns: 
    - column: SettingKey 
    - column: CreatedAt 
    - column: Channel 
    - column: SettingValue 
    - column: UpdatedAt 
The table should have the title "ChannelSettings" und the data must be loaded from the server with the following relative URL: 
    "/ChannelService/channelsetting/channel/{id}" 
Add a HTML table to the view with the following ChannelMember columns: 
    - column: User 
    - column: Channel 
    - column: CreatedAt 
    - column: Role 
The table should have the title "ChannelMembers" und the data must be loaded from the server with the following relative URL: 
    "/UserService/channelmember/channel/{id}" 
Add a HTML table to the view with the following Video columns: 
    - column: ResolutionHeight 
    - column: VisibilityRegionRestrictionJson 
    - column: DefaultCaptionLanguage 
    - column: PrivacyStatus 
    - column: Language 
    - column: MadeForKids 
    - column: ThumbnailDefault 
    - column: CreatedAt 
    - column: Title 
    - column: FrameRate 
    - column: CommentCountCached 
    - column: Category 
    - column: ResolutionWidth 
    - column: ThumbnailMedium 
    - column: OriginalFileName 
    - column: UpdatedAt 
    - column: LikeCountCached 
    - column: ThumbnailHigh 
    - column: ViewCountCached 
    - column: PublishedAt 
    - column: Channel 
    - column: DurationSeconds 
    - column: Status 
    - column: FilePathOrStorageKey 
    - column: LicenseType 
    - column: Description 
The table should have the title "Videos" und the data must be loaded from the server with the following relative URL: 
    "/VideoService/video/channel/{id}" 
Add a HTML table to the view with the following UserFeedItem columns: 
    - column: ShownAt 
    - column: Video 
    - column: RankScore 
    - column: Channel 
    - column: User 
    - column: ClickedAt 
    - column: ItemType 
The table should have the title "UserFeedItems" und the data must be loaded from the server with the following relative URL: 
    "/ChannelService/userfeeditem/channel/{id}" 
Add a HTML table to the view with the following Subscription columns: 
    - column: IsActive 
    - column: Channel 
    - column: NotificationsLevel 
    - column: SubscriberUser 
    - column: CreatedAt 
The table should have the title "Subscriptions" und the data must be loaded from the server with the following relative URL: 
    "/ChannelService/subscription/channel/{id}" 
Add a HTML table to the view with the following Playlist columns: 
    - column: IsSystemGenerated 
    - column: CreatedAt 
    - column: UpdatedAt 
    - column: PrivacyStatus 
    - column: Title 
    - column: Description 
    - column: Channel 
The table should have the title "Playlists" und the data must be loaded from the server with the following relative URL: 
    "/PlaylistService/playlist/channel/{id}"

3. The ChannelSettingView must contain the following fields: 
    - name: Channel   type: Channel 
    - name: CreatedAt   type: DATE 
    - name: SettingKey   type: STRING 
    - name: SettingValue   type: STRING 
    - name: UpdatedAt   type: DATE 
The data source for the [Channel] select control should be loaded from the relative URL: 
    "/ChannelService/channel"   (HTTP-GET) 
An existing ChannelSetting entity should be loaded from the relative URL: 
    "/ChannelService/channelsetting/{id}"   (HTTP-GET) 
If a new ChannelSetting entity has been created, the new entity should be posted to the relative URL: 
    "/ChannelService/channelsetting"   (HTTP-POST) 
If an existing ChannelSetting entity has been updated, the modified entity should be sent to the relative URL: 
    "/ChannelService/channelsetting/{id}"   (HTTP-PUT) 
If an existing ChannelSetting entity has to be deleted, the following relative URL should be called: 
    "/ChannelService/channelsetting/{id}"   (HTTP-DELETE)

4. The SubscriptionView must contain the following fields: 
    - name: Channel   type: Channel 
    - name: CreatedAt   type: DATE 
    - name: IsActive   type: BOOL 
    - name: NotificationsLevel   type: STRING 
    - name: SubscriberUser   type: User 
The data source for the [Channel] select control should be loaded from the relative URL: 
    "/ChannelService/channel"   (HTTP-GET) 
The data source for the [SubscriberUser] select control should be loaded from the relative URL: 
    "/UserService/user"   (HTTP-GET) 
An existing Subscription entity should be loaded from the relative URL: 
    "/ChannelService/subscription/{id}"   (HTTP-GET) 
If a new Subscription entity has been created, the new entity should be posted to the relative URL: 
    "/ChannelService/subscription"   (HTTP-POST) 
If an existing Subscription entity has been updated, the modified entity should be sent to the relative URL: 
    "/ChannelService/subscription/{id}"   (HTTP-PUT) 
If an existing Subscription entity has to be deleted, the following relative URL should be called: 
    "/ChannelService/subscription/{id}"   (HTTP-DELETE)

5. The UserFeedItemView must contain the following fields: 
    - name: Channel   type: Channel 
    - name: ClickedAt   type: DATE 
    - name: ItemType   type: STRING 
    - name: RankScore   type: DOUBLE 
    - name: ShownAt   type: DATE 
    - name: User   type: User 
    - name: Video   type: Video 
The data source for the [User] select control should be loaded from the relative URL: 
    "/UserService/user"   (HTTP-GET) 
The data source for the [Video] select control should be loaded from the relative URL: 
    "/VideoService/video"   (HTTP-GET) 
The data source for the [Channel] select control should be loaded from the relative URL: 
    "/ChannelService/channel"   (HTTP-GET) 
An existing UserFeedItem entity should be loaded from the relative URL: 
    "/ChannelService/userfeeditem/{id}"   (HTTP-GET) 
If a new UserFeedItem entity has been created, the new entity should be posted to the relative URL: 
    "/ChannelService/userfeeditem"   (HTTP-POST) 
If an existing UserFeedItem entity has been updated, the modified entity should be sent to the relative URL: 
    "/ChannelService/userfeeditem/{id}"   (HTTP-PUT) 
If an existing UserFeedItem entity has to be deleted, the following relative URL should be called: 
    "/ChannelService/userfeeditem/{id}"   (HTTP-DELETE)