Prompt for the StoryApp

Please create a React-JS application for the StoryModule. The application  has to offer the following views for the user interface: 
    1. AdPlacementView 
    2. ArchiveItemView 
    3. CommentView 
    4. ReportView 
    5. StoryView 
    6. StoryMediaView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 6 views are defined below.

1. The AdPlacementView must contain the following fields: 
    - name: AdCampaign   type: AdCampaign 
    - name: Clicks   type: LONG 
    - name: CreatedAt   type: DATE 
    - name: Impressions   type: LONG 
    - name: PlacementType   type: STRING 
    - name: Post   type: Post 
    - name: Reel   type: Reel 
    - name: Story   type: Story 
The data source for the [Post] select control should be loaded from the relative URL: 
    "/UserAccountService/post"   (HTTP-GET) 
The data source for the [AdCampaign] select control should be loaded from the relative URL: 
    "/ReelService/adcampaign"   (HTTP-GET) 
The data source for the [Reel] select control should be loaded from the relative URL: 
    "/ReelService/reel"   (HTTP-GET) 
The data source for the [Story] select control should be loaded from the relative URL: 
    "/StoryService/story"   (HTTP-GET) 
An existing AdPlacement entity should be loaded from the relative URL: 
    "/StoryService/adplacement/{id}"   (HTTP-GET) 
If a new AdPlacement entity has been created, the new entity should be posted to the relative URL: 
    "/StoryService/adplacement"   (HTTP-POST) 
If an existing AdPlacement entity has been updated, the modified entity should be sent to the relative URL: 
    "/StoryService/adplacement/{id}"   (HTTP-PUT) 
If an existing AdPlacement entity has to be deleted, the following relative URL should be called: 
    "/StoryService/adplacement/{id}"   (HTTP-DELETE)

2. The ArchiveItemView must contain the following fields: 
    - name: ArchivedAt   type: DATE 
    - name: ItemType   type: STRING 
    - name: Post   type: Post 
    - name: Reel   type: Reel 
    - name: Story   type: Story 
    - name: UserAccount   type: UserAccount 
The data source for the [Post] select control should be loaded from the relative URL: 
    "/UserAccountService/post"   (HTTP-GET) 
The data source for the [Reel] select control should be loaded from the relative URL: 
    "/ReelService/reel"   (HTTP-GET) 
The data source for the [Story] select control should be loaded from the relative URL: 
    "/StoryService/story"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing ArchiveItem entity should be loaded from the relative URL: 
    "/StoryService/archiveitem/{id}"   (HTTP-GET) 
If a new ArchiveItem entity has been created, the new entity should be posted to the relative URL: 
    "/StoryService/archiveitem"   (HTTP-POST) 
If an existing ArchiveItem entity has been updated, the modified entity should be sent to the relative URL: 
    "/StoryService/archiveitem/{id}"   (HTTP-PUT) 
If an existing ArchiveItem entity has to be deleted, the following relative URL should be called: 
    "/StoryService/archiveitem/{id}"   (HTTP-DELETE)

3. The CommentView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: IsDeleted   type: BOOL 
    - name: IsPinned   type: BOOL 
    - name: ParentComment   type: LONG 
    - name: Post   type: Post 
    - name: Text   type: STRING 
    - name: UpdatedAt   type: DATE 
    - name: UserAccount   type: UserAccount 
The data source for the [Post] select control should be loaded from the relative URL: 
    "/UserAccountService/post"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing Comment entity should be loaded from the relative URL: 
    "/StoryService/comment/{id}"   (HTTP-GET) 
If a new Comment entity has been created, the new entity should be posted to the relative URL: 
    "/StoryService/comment"   (HTTP-POST) 
If an existing Comment entity has been updated, the modified entity should be sent to the relative URL: 
    "/StoryService/comment/{id}"   (HTTP-PUT) 
If an existing Comment entity has to be deleted, the following relative URL should be called: 
    "/StoryService/comment/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following CommentLike columns: 
    - column: CreatedAt 
    - column: Comment 
    - column: UserAccount 
The table should have the title "CommentLikes" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/commentlike/comment/{id}" 
Add a HTML table to the view with the following Notification columns: 
    - column: Post 
    - column: Story 
    - column: SourceUser 
    - column: Reel 
    - column: Type 
    - column: Comment 
    - column: DirectMessage 
    - column: IsRead 
    - column: CreatedAt 
    - column: UserAccount 
The table should have the title "Notifications" und the data must be loaded from the server with the following relative URL: 
    "/ReelService/notification/comment/{id}" 
Add a HTML table to the view with the following Report columns: 
    - column: ReportedUser 
    - column: Reporter 
    - column: Post 
    - column: CreatedAt 
    - column: Reel 
    - column: Comment 
    - column: Story 
    - column: Status 
    - column: Reason 
    - column: Details 
    - column: UpdatedAt 
The table should have the title "Reports" und the data must be loaded from the server with the following relative URL: 
    "/StoryService/report/comment/{id}"

4. The ReportView must contain the following fields: 
    - name: Comment   type: Comment 
    - name: CreatedAt   type: DATE 
    - name: Details   type: STRING 
    - name: Post   type: Post 
    - name: Reason   type: STRING 
    - name: Reel   type: Reel 
    - name: ReportedUser   type: UserAccount 
    - name: Reporter   type: UserAccount 
    - name: Status   type: STRING 
    - name: Story   type: Story 
    - name: UpdatedAt   type: DATE 
The data source for the [Comment] select control should be loaded from the relative URL: 
    "/StoryService/comment"   (HTTP-GET) 
The data source for the [ReportedUser] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
The data source for the [Post] select control should be loaded from the relative URL: 
    "/UserAccountService/post"   (HTTP-GET) 
The data source for the [Reporter] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
The data source for the [Reel] select control should be loaded from the relative URL: 
    "/ReelService/reel"   (HTTP-GET) 
The data source for the [Story] select control should be loaded from the relative URL: 
    "/StoryService/story"   (HTTP-GET) 
An existing Report entity should be loaded from the relative URL: 
    "/StoryService/report/{id}"   (HTTP-GET) 
If a new Report entity has been created, the new entity should be posted to the relative URL: 
    "/StoryService/report"   (HTTP-POST) 
If an existing Report entity has been updated, the modified entity should be sent to the relative URL: 
    "/StoryService/report/{id}"   (HTTP-PUT) 
If an existing Report entity has to be deleted, the following relative URL should be called: 
    "/StoryService/report/{id}"   (HTTP-DELETE)

5. The StoryView must contain the following fields: 
    - name: Caption   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: ExpiresAt   type: DATE 
    - name: HighlightTitle   type: STRING 
    - name: IsCloseFriendsOnly   type: BOOL 
    - name: IsHighlight   type: BOOL 
    - name: UserAccount   type: UserAccount 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing Story entity should be loaded from the relative URL: 
    "/StoryService/story/{id}"   (HTTP-GET) 
If a new Story entity has been created, the new entity should be posted to the relative URL: 
    "/StoryService/story"   (HTTP-POST) 
If an existing Story entity has been updated, the modified entity should be sent to the relative URL: 
    "/StoryService/story/{id}"   (HTTP-PUT) 
If an existing Story entity has to be deleted, the following relative URL should be called: 
    "/StoryService/story/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following DirectMessage columns: 
    - column: Reel 
    - column: MediaUrl 
    - column: Post 
    - column: Sender 
    - column: Story 
    - column: ReplyToMessage 
    - column: DirectThread 
    - column: SeenAt 
    - column: CreatedAt 
    - column: Text 
    - column: MessageType 
    - column: IsSeen 
The table should have the title "DirectMessages" und the data must be loaded from the server with the following relative URL: 
    "/DirectThreadService/directmessage/story/{id}" 
Add a HTML table to the view with the following StoryView columns: 
    - column: ViewedAt 
    - column: Story 
    - column: Viewer 
The table should have the title "StoryViews" und the data must be loaded from the server with the following relative URL: 
    "/FeatureFlagService/storyview/story/{id}" 
Add a HTML table to the view with the following StoryMedia columns: 
    - column: CreatedAt 
    - column: ThumbnailUrl 
    - column: MediaOrder 
    - column: FilterName 
    - column: Url 
    - column: DurationSeconds 
    - column: MediaType 
    - column: Story 
The table should have the title "StoryMedias" und the data must be loaded from the server with the following relative URL: 
    "/StoryService/storymedia/story/{id}" 
Add a HTML table to the view with the following Notification columns: 
    - column: Post 
    - column: Story 
    - column: SourceUser 
    - column: Reel 
    - column: Type 
    - column: Comment 
    - column: DirectMessage 
    - column: IsRead 
    - column: CreatedAt 
    - column: UserAccount 
The table should have the title "Notifications" und the data must be loaded from the server with the following relative URL: 
    "/ReelService/notification/story/{id}" 
Add a HTML table to the view with the following Report columns: 
    - column: ReportedUser 
    - column: Reporter 
    - column: Post 
    - column: CreatedAt 
    - column: Reel 
    - column: Comment 
    - column: Story 
    - column: Status 
    - column: Reason 
    - column: Details 
    - column: UpdatedAt 
The table should have the title "Reports" und the data must be loaded from the server with the following relative URL: 
    "/StoryService/report/story/{id}" 
Add a HTML table to the view with the following ArchiveItem columns: 
    - column: UserAccount 
    - column: Post 
    - column: ItemType 
    - column: Story 
    - column: ArchivedAt 
    - column: Reel 
The table should have the title "ArchiveItems" und the data must be loaded from the server with the following relative URL: 
    "/StoryService/archiveitem/story/{id}" 
Add a HTML table to the view with the following AdPlacement columns: 
    - column: Post 
    - column: Clicks 
    - column: Impressions 
    - column: CreatedAt 
    - column: Reel 
    - column: AdCampaign 
    - column: PlacementType 
    - column: Story 
The table should have the title "AdPlacements" und the data must be loaded from the server with the following relative URL: 
    "/StoryService/adplacement/story/{id}"

6. The StoryMediaView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: DurationSeconds   type: LONG 
    - name: FilterName   type: STRING 
    - name: MediaOrder   type: LONG 
    - name: MediaType   type: STRING 
    - name: Story   type: Story 
    - name: ThumbnailUrl   type: STRING 
    - name: Url   type: STRING 
The data source for the [Story] select control should be loaded from the relative URL: 
    "/StoryService/story"   (HTTP-GET) 
An existing StoryMedia entity should be loaded from the relative URL: 
    "/StoryService/storymedia/{id}"   (HTTP-GET) 
If a new StoryMedia entity has been created, the new entity should be posted to the relative URL: 
    "/StoryService/storymedia"   (HTTP-POST) 
If an existing StoryMedia entity has been updated, the modified entity should be sent to the relative URL: 
    "/StoryService/storymedia/{id}"   (HTTP-PUT) 
If an existing StoryMedia entity has to be deleted, the following relative URL should be called: 
    "/StoryService/storymedia/{id}"   (HTTP-DELETE)