Prompt for the MessageApp

Please create a React-JS application for the MessageModule. The application  has to offer the following views for the user interface: 
    1. AttachmentView 
    2. DeviceView 
    3. MessageView 
    4. MessageRecipientView 
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 AttachmentView must contain the following fields: 
    - name: Blurhash   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: EncryptionKey   type: STRING 
    - name: EncryptionNonce   type: STRING 
    - name: FileName   type: STRING 
    - name: Message   type: Message 
    - name: MimeType   type: STRING 
    - name: RemoteStorageUrl   type: STRING 
    - name: SizeBytes   type: LONG 
    - name: ThumbnailUrl   type: STRING 
The data source for the [Message] select control should be loaded from the relative URL: 
    "/MessageService/message"   (HTTP-GET) 
An existing Attachment entity should be loaded from the relative URL: 
    "/MessageService/attachment/{id}"   (HTTP-GET) 
If a new Attachment entity has been created, the new entity should be posted to the relative URL: 
    "/MessageService/attachment"   (HTTP-POST) 
If an existing Attachment entity has been updated, the modified entity should be sent to the relative URL: 
    "/MessageService/attachment/{id}"   (HTTP-PUT) 
If an existing Attachment entity has to be deleted, the following relative URL should be called: 
    "/MessageService/attachment/{id}"   (HTTP-DELETE)

2. The DeviceView must contain the following fields: 
    - name: IsActive   type: BOOL 
    - name: IsPrimary   type: BOOL 
    - name: LastSeenAt   type: DATE 
    - name: LinkedAt   type: DATE 
    - name: Name   type: STRING 
    - name: Platform   type: STRING 
    - name: PushToken   type: STRING 
    - name: UnlinkedAt   type: DATE 
    - 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: 
    "/MessageService/device/{id}"   (HTTP-GET) 
If a new Device entity has been created, the new entity should be posted to the relative URL: 
    "/MessageService/device"   (HTTP-POST) 
If an existing Device entity has been updated, the modified entity should be sent to the relative URL: 
    "/MessageService/device/{id}"   (HTTP-PUT) 
If an existing Device entity has to be deleted, the following relative URL should be called: 
    "/MessageService/device/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following ServerLogEntry columns: 
    - column: EventType 
    - column: UserAccount 
    - column: Conversation 
    - column: LogLevel 
    - column: Device 
    - column: Message 
    - column: ServerNode 
    - column: CreatedAt 
The table should have the title "ServerLogEntrys" und the data must be loaded from the server with the following relative URL: 
    "/ServerNodeService/serverlogentry/device/{id}" 
Add a HTML table to the view with the following DeviceKey columns: 
    - column: Device 
    - column: PublicKey 
    - column: IsCurrent 
    - column: CreatedAt 
The table should have the title "DeviceKeys" und the data must be loaded from the server with the following relative URL: 
    "/CallDurationService/devicekey/device/{id}" 
Add a HTML table to the view with the following MessageRecipient columns: 
    - column: DeliveredAt 
    - column: Device 
    - column: DeliveryStatus 
    - column: RecipientUserAccount 
    - column: ReadAt 
    - column: FailureReason 
    - column: Message 
The table should have the title "MessageRecipients" und the data must be loaded from the server with the following relative URL: 
    "/MessageService/messagerecipient/device/{id}" 
Add a HTML table to the view with the following EncryptionKeyBundle columns: 
    - column: IdentityKey 
    - column: CreatedAt 
    - column: Device 
    - column: UserAccount 
    - column: BundleVersion 
The table should have the title "EncryptionKeyBundles" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/encryptionkeybundle/device/{id}" 
Add a HTML table to the view with the following PreKey columns: 
    - column: ConsumedAt 
    - column: IsSigned 
    - column: Device 
    - column: CreatedAt 
    - column: PublicKey 
    - column: KeyId 
The table should have the title "PreKeys" und the data must be loaded from the server with the following relative URL: 
    "/ServerNodeService/prekey/device/{id}"

3. The MessageView must contain the following fields: 
    - name: Body   type: STRING 
    - name: ClientMessageUuid   type: STRING 
    - name: Conversation   type: Conversation 
    - name: IsDeletedForSender   type: BOOL 
    - name: IsSystemMessage   type: BOOL 
    - name: MessageType   type: STRING 
    - name: ReplyToMessage   type: LONG 
    - name: SenderUserAccount   type: LONG 
    - name: SentAt   type: DATE 
    - name: ServerReceivedAt   type: DATE 
The data source for the [Conversation] select control should be loaded from the relative URL: 
    "/ConversationService/conversation"   (HTTP-GET) 
An existing Message entity should be loaded from the relative URL: 
    "/MessageService/message/{id}"   (HTTP-GET) 
If a new Message entity has been created, the new entity should be posted to the relative URL: 
    "/MessageService/message"   (HTTP-POST) 
If an existing Message entity has been updated, the modified entity should be sent to the relative URL: 
    "/MessageService/message/{id}"   (HTTP-PUT) 
If an existing Message entity has to be deleted, the following relative URL should be called: 
    "/MessageService/message/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Reaction columns: 
    - column: EmojiCode 
    - column: UserAccount 
    - column: Message 
    - column: CreatedAt 
The table should have the title "Reactions" und the data must be loaded from the server with the following relative URL: 
    "/SafetyNumberService/reaction/message/{id}" 
Add a HTML table to the view with the following ServerLogEntry columns: 
    - column: EventType 
    - column: UserAccount 
    - column: Conversation 
    - column: LogLevel 
    - column: Device 
    - column: Message 
    - column: ServerNode 
    - column: CreatedAt 
The table should have the title "ServerLogEntrys" und the data must be loaded from the server with the following relative URL: 
    "/ServerNodeService/serverlogentry/message/{id}" 
Add a HTML table to the view with the following AbuseReport columns: 
    - column: HandlerNote 
    - column: Category 
    - column: GroupChat 
    - column: Description 
    - column: CreatedAt 
    - column: ReporterUserAccount 
    - column: Message 
    - column: ReportedUserAccount 
    - column: HandledAt 
The table should have the title "AbuseReports" und the data must be loaded from the server with the following relative URL: 
    "/ConversationService/abusereport/message/{id}" 
Add a HTML table to the view with the following MessageRecipient columns: 
    - column: DeliveredAt 
    - column: Device 
    - column: DeliveryStatus 
    - column: RecipientUserAccount 
    - column: ReadAt 
    - column: FailureReason 
    - column: Message 
The table should have the title "MessageRecipients" und the data must be loaded from the server with the following relative URL: 
    "/MessageService/messagerecipient/message/{id}" 
Add a HTML table to the view with the following Attachment columns: 
    - column: Blurhash 
    - column: RemoteStorageUrl 
    - column: ThumbnailUrl 
    - column: FileName 
    - column: CreatedAt 
    - column: EncryptionNonce 
    - column: SizeBytes 
    - column: MimeType 
    - column: Message 
    - column: EncryptionKey 
The table should have the title "Attachments" und the data must be loaded from the server with the following relative URL: 
    "/MessageService/attachment/message/{id}"

4. The MessageRecipientView must contain the following fields: 
    - name: DeliveredAt   type: DATE 
    - name: DeliveryStatus   type: STRING 
    - name: Device   type: Device 
    - name: FailureReason   type: STRING 
    - name: Message   type: Message 
    - name: ReadAt   type: DATE 
    - name: RecipientUserAccount   type: LONG 
The data source for the [Message] select control should be loaded from the relative URL: 
    "/MessageService/message"   (HTTP-GET) 
The data source for the [Device] select control should be loaded from the relative URL: 
    "/MessageService/device"   (HTTP-GET) 
An existing MessageRecipient entity should be loaded from the relative URL: 
    "/MessageService/messagerecipient/{id}"   (HTTP-GET) 
If a new MessageRecipient entity has been created, the new entity should be posted to the relative URL: 
    "/MessageService/messagerecipient"   (HTTP-POST) 
If an existing MessageRecipient entity has been updated, the modified entity should be sent to the relative URL: 
    "/MessageService/messagerecipient/{id}"   (HTTP-PUT) 
If an existing MessageRecipient entity has to be deleted, the following relative URL should be called: 
    "/MessageService/messagerecipient/{id}"   (HTTP-DELETE)