Prompt for the CategoryApp

Please create a React-JS application for the CategoryModule. The application  has to offer the following views for the user interface: 
    1. CategoryView 
    2. NotificationView 
    3. PlaylistView 
    4. PlaylistVideoView 
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 CategoryView must contain the following fields: 
    - name: Description   type: STRING 
    - name: IsActive   type: BOOL 
    - name: Name   type: STRING 
An existing Category entity should be loaded from the relative URL: 
    "/CategoryService/category/{id}"   (HTTP-GET) 
If a new Category entity has been created, the new entity should be posted to the relative URL: 
    "/CategoryService/category"   (HTTP-POST) 
If an existing Category entity has been updated, the modified entity should be sent to the relative URL: 
    "/CategoryService/category/{id}"   (HTTP-PUT) 
If an existing Category entity has to be deleted, the following relative URL should be called: 
    "/CategoryService/category/{id}"   (HTTP-DELETE) 
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/category/{id}"

2. The NotificationView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: IsRead   type: BOOL 
    - name: PayloadJson   type: STRING 
    - name: Type   type: STRING 
    - 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 Notification entity should be loaded from the relative URL: 
    "/CategoryService/notification/{id}"   (HTTP-GET) 
If a new Notification entity has been created, the new entity should be posted to the relative URL: 
    "/CategoryService/notification"   (HTTP-POST) 
If an existing Notification entity has been updated, the modified entity should be sent to the relative URL: 
    "/CategoryService/notification/{id}"   (HTTP-PUT) 
If an existing Notification entity has to be deleted, the following relative URL should be called: 
    "/CategoryService/notification/{id}"   (HTTP-DELETE)

3. 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: 
    "/CategoryService/playlist/{id}"   (HTTP-GET) 
If a new Playlist entity has been created, the new entity should be posted to the relative URL: 
    "/CategoryService/playlist"   (HTTP-POST) 
If an existing Playlist entity has been updated, the modified entity should be sent to the relative URL: 
    "/CategoryService/playlist/{id}"   (HTTP-PUT) 
If an existing Playlist entity has to be deleted, the following relative URL should be called: 
    "/CategoryService/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: 
    "/CategoryService/playlistvideo/playlist/{id}"

4. 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: 
    "/CategoryService/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: 
    "/CategoryService/playlistvideo/{id}"   (HTTP-GET) 
If a new PlaylistVideo entity has been created, the new entity should be posted to the relative URL: 
    "/CategoryService/playlistvideo"   (HTTP-POST) 
If an existing PlaylistVideo entity has been updated, the modified entity should be sent to the relative URL: 
    "/CategoryService/playlistvideo/{id}"   (HTTP-PUT) 
If an existing PlaylistVideo entity has to be deleted, the following relative URL should be called: 
    "/CategoryService/playlistvideo/{id}"   (HTTP-DELETE)