Prompt for the PlaylistApp

Please create a React-JS application for the PlaylistModule. The application  has to offer the following views for the user interface: 
    1. DailyVideoMetricView 
    2. PlaylistView 
    3. PlaylistVideoView 
    4. UserProfileView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below.

1. The DailyVideoMetricView must contain the following fields: 
    - name: CommentCount   type: LONG 
    - name: Date   type: DATE 
    - name: DislikeCount   type: LONG 
    - name: LikeCount   type: LONG 
    - name: RevenueMicros   type: LONG 
    - name: ShareCount   type: LONG 
    - name: UniqueViewerCountApprox   type: LONG 
    - name: Video   type: Video 
    - name: ViewCount   type: LONG 
    - name: WatchTimeSeconds   type: LONG 
The data source for the [Video] select control should be loaded from the relative URL: 
    "/VideoService/video"   (HTTP-GET) 
An existing DailyVideoMetric entity should be loaded from the relative URL: 
    "/PlaylistService/dailyvideometric/{id}"   (HTTP-GET) 
If a new DailyVideoMetric entity has been created, the new entity should be posted to the relative URL: 
    "/PlaylistService/dailyvideometric"   (HTTP-POST) 
If an existing DailyVideoMetric entity has been updated, the modified entity should be sent to the relative URL: 
    "/PlaylistService/dailyvideometric/{id}"   (HTTP-PUT) 
If an existing DailyVideoMetric entity has to be deleted, the following relative URL should be called: 
    "/PlaylistService/dailyvideometric/{id}"   (HTTP-DELETE)

2. The PlaylistView must contain the following fields: 
    - name: Channel   type: Channel 
    - name: CreatedAt   type: DATE 
    - name: Description   type: STRING 
    - name: IsSystemGenerated   type: BOOL 
    - name: PrivacyStatus   type: STRING 
    - name: Title   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 Playlist entity should be loaded from the relative URL: 
    "/PlaylistService/playlist/{id}"   (HTTP-GET) 
If a new Playlist entity has been created, the new entity should be posted to the relative URL: 
    "/PlaylistService/playlist"   (HTTP-POST) 
If an existing Playlist entity has been updated, the modified entity should be sent to the relative URL: 
    "/PlaylistService/playlist/{id}"   (HTTP-PUT) 
If an existing Playlist entity has to be deleted, the following relative URL should be called: 
    "/PlaylistService/playlist/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following PlaylistVideo columns: 
    - column: Playlist 
    - column: AddedByUser 
    - column: Video 
    - column: AddedAt 
    - column: Position 
The table should have the title "PlaylistVideos" und the data must be loaded from the server with the following relative URL: 
    "/PlaylistService/playlistvideo/playlist/{id}"

3. The PlaylistVideoView must contain the following fields: 
    - name: AddedAt   type: DATE 
    - name: AddedByUser   type: User 
    - name: Playlist   type: Playlist 
    - name: Position   type: LONG 
    - name: Video   type: Video 
The data source for the [Playlist] select control should be loaded from the relative URL: 
    "/PlaylistService/playlist"   (HTTP-GET) 
The data source for the [AddedByUser] 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) 
An existing PlaylistVideo entity should be loaded from the relative URL: 
    "/PlaylistService/playlistvideo/{id}"   (HTTP-GET) 
If a new PlaylistVideo entity has been created, the new entity should be posted to the relative URL: 
    "/PlaylistService/playlistvideo"   (HTTP-POST) 
If an existing PlaylistVideo entity has been updated, the modified entity should be sent to the relative URL: 
    "/PlaylistService/playlistvideo/{id}"   (HTTP-PUT) 
If an existing PlaylistVideo entity has to be deleted, the following relative URL should be called: 
    "/PlaylistService/playlistvideo/{id}"   (HTTP-DELETE)

4. The UserProfileView must contain the following fields: 
    - name: AdditionalSettingsJson   type: STRING 
    - name: BannerImageUrl   type: STRING 
    - name: Bio   type: STRING 
    - name: Birthdate   type: DATE 
    - name: CreatedAt   type: DATE 
    - name: Gender   type: STRING 
    - name: LinksJson   type: STRING 
    - name: UpdatedAt   type: DATE 
    - name: User   type: User 
The data source for the [User] select control should be loaded from the relative URL: 
    "/UserService/user"   (HTTP-GET) 
An existing UserProfile entity should be loaded from the relative URL: 
    "/PlaylistService/userprofile/{id}"   (HTTP-GET) 
If a new UserProfile entity has been created, the new entity should be posted to the relative URL: 
    "/PlaylistService/userprofile"   (HTTP-POST) 
If an existing UserProfile entity has been updated, the modified entity should be sent to the relative URL: 
    "/PlaylistService/userprofile/{id}"   (HTTP-PUT) 
If an existing UserProfile entity has to be deleted, the following relative URL should be called: 
    "/PlaylistService/userprofile/{id}"   (HTTP-DELETE)