Overview
Summary
Contact
Donate
Imprint
Prompt for the
DirectThreadApp
Please create a React-JS application for the DirectThreadModule. The application has to offer the following views for the user interface: 1. DeviceView 2. DirectMessageView 3. DirectThreadView 4. PostLikeView 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 DeviceView must contain the following fields: - name: AppVersion type: STRING - name: CreatedAt type: DATE - name: IsPushEnabled type: BOOL - name: LastActiveAt type: DATE - name: OsVersion type: STRING - name: Platform type: STRING - 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 Device entity should be loaded from the relative URL: "/DirectThreadService/device/{id}" (HTTP-GET) If a new Device entity has been created, the new entity should be posted to the relative URL: "/DirectThreadService/device" (HTTP-POST) If an existing Device entity has been updated, the modified entity should be sent to the relative URL: "/DirectThreadService/device/{id}" (HTTP-PUT) If an existing Device entity has to be deleted, the following relative URL should be called: "/DirectThreadService/device/{id}" (HTTP-DELETE) 2. The DirectMessageView must contain the following fields: - name: CreatedAt type: DATE - name: DirectThread type: DirectThread - name: IsSeen type: BOOL - name: MediaUrl type: STRING - name: MessageType type: STRING - name: Post type: Post - name: Reel type: Reel - name: ReplyToMessage type: LONG - name: SeenAt type: DATE - name: Sender type: UserAccount - name: Story type: Story - name: Text type: STRING The data source for the [Sender] 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 [Reel] select control should be loaded from the relative URL: "/ReelService/reel" (HTTP-GET) The data source for the [DirectThread] select control should be loaded from the relative URL: "/DirectThreadService/directthread" (HTTP-GET) The data source for the [Story] select control should be loaded from the relative URL: "/StoryService/story" (HTTP-GET) An existing DirectMessage entity should be loaded from the relative URL: "/DirectThreadService/directmessage/{id}" (HTTP-GET) If a new DirectMessage entity has been created, the new entity should be posted to the relative URL: "/DirectThreadService/directmessage" (HTTP-POST) If an existing DirectMessage entity has been updated, the modified entity should be sent to the relative URL: "/DirectThreadService/directmessage/{id}" (HTTP-PUT) If an existing DirectMessage entity has to be deleted, the following relative URL should be called: "/DirectThreadService/directmessage/{id}" (HTTP-DELETE) 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/directmessage/{id}" 3. The DirectThreadView must contain the following fields: - name: CreatedAt type: DATE - name: IsGroup type: BOOL - name: Title type: STRING An existing DirectThread entity should be loaded from the relative URL: "/DirectThreadService/directthread/{id}" (HTTP-GET) If a new DirectThread entity has been created, the new entity should be posted to the relative URL: "/DirectThreadService/directthread" (HTTP-POST) If an existing DirectThread entity has been updated, the modified entity should be sent to the relative URL: "/DirectThreadService/directthread/{id}" (HTTP-PUT) If an existing DirectThread entity has to be deleted, the following relative URL should be called: "/DirectThreadService/directthread/{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/directthread/{id}" Add a HTML table to the view with the following DirectThreadParticipant columns: - column: UserAccount - column: DirectThread - column: JoinedAt - column: IsAdmin The table should have the title "DirectThreadParticipants" und the data must be loaded from the server with the following relative URL: "/UserAccountService/directthreadparticipant/directthread/{id}" 4. The PostLikeView must contain the following fields: - name: CreatedAt type: DATE - name: Post type: Post - 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 PostLike entity should be loaded from the relative URL: "/DirectThreadService/postlike/{id}" (HTTP-GET) If a new PostLike entity has been created, the new entity should be posted to the relative URL: "/DirectThreadService/postlike" (HTTP-POST) If an existing PostLike entity has been updated, the modified entity should be sent to the relative URL: "/DirectThreadService/postlike/{id}" (HTTP-PUT) If an existing PostLike entity has to be deleted, the following relative URL should be called: "/DirectThreadService/postlike/{id}" (HTTP-DELETE)
Copy prompt
Overview
Summary
Contact
Donate
Imprint