Prompt for the CommentApp

Please create a React-JS application for the CommentModule. The application  has to offer the following views for the user interface: 
    1. CommentView 
    2. CommentLikeView 
    3. DailyVideoMetricView 
    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 CommentView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: IsEdited   type: BOOL 
    - name: IsPinned   type: BOOL 
    - name: LikeCountCached   type: LONG 
    - name: ParentComment   type: LONG 
    - name: Status   type: STRING 
    - name: Text   type: STRING 
    - name: UpdatedAt   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) 
An existing Comment entity should be loaded from the relative URL: 
    "/CommentService/comment/{id}"   (HTTP-GET) 
If a new Comment entity has been created, the new entity should be posted to the relative URL: 
    "/CommentService/comment"   (HTTP-POST) 
If an existing Comment entity has been updated, the modified entity should be sent to the relative URL: 
    "/CommentService/comment/{id}"   (HTTP-PUT) 
If an existing Comment entity has to be deleted, the following relative URL should be called: 
    "/CommentService/comment/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following CommentLike columns: 
    - column: CreatedAt 
    - column: Type 
    - column: Comment 
    - column: User 
The table should have the title "CommentLikes" und the data must be loaded from the server with the following relative URL: 
    "/CommentService/commentlike/comment/{id}" 
Add a HTML table to the view with the following CommentReport columns: 
    - column: ReporterUser 
    - column: ResolvedAt 
    - column: Status 
    - column: CreatedAt 
    - column: Comment 
    - column: ReasonCode 
    - column: ResolvedByUser 
    - column: Description 
The table should have the title "CommentReports" und the data must be loaded from the server with the following relative URL: 
    "/UserService/commentreport/comment/{id}"

2. The CommentLikeView must contain the following fields: 
    - name: Comment   type: Comment 
    - name: CreatedAt   type: DATE 
    - name: Type   type: STRING 
    - name: User   type: User 
The data source for the [Comment] select control should be loaded from the relative URL: 
    "/CommentService/comment"   (HTTP-GET) 
The data source for the [User] select control should be loaded from the relative URL: 
    "/UserService/user"   (HTTP-GET) 
An existing CommentLike entity should be loaded from the relative URL: 
    "/CommentService/commentlike/{id}"   (HTTP-GET) 
If a new CommentLike entity has been created, the new entity should be posted to the relative URL: 
    "/CommentService/commentlike"   (HTTP-POST) 
If an existing CommentLike entity has been updated, the modified entity should be sent to the relative URL: 
    "/CommentService/commentlike/{id}"   (HTTP-PUT) 
If an existing CommentLike entity has to be deleted, the following relative URL should be called: 
    "/CommentService/commentlike/{id}"   (HTTP-DELETE)

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