Prompt for the UserAccountApp

Please create a React-JS application for the UserAccountModule. The application  has to offer the following views for the user interface: 
    1. ChannelView 
    2. MessageView 
    3. NitroSubscriptionView 
    4. ServerView 
    5. UserAccountView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 5 views are defined below.

1. The ChannelView must contain the following fields: 
    - name: Bitrate   type: LONG 
    - name: Category   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: IsNsfw   type: BOOL 
    - name: Name   type: STRING 
    - name: Position   type: LONG 
    - name: Server   type: Server 
    - name: Type   type: STRING 
    - name: UserLimit   type: LONG 
The data source for the [Server] select control should be loaded from the relative URL: 
    "/UserAccountService/server"   (HTTP-GET) 
An existing Channel entity should be loaded from the relative URL: 
    "/UserAccountService/channel/{id}"   (HTTP-GET) 
If a new Channel entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/channel"   (HTTP-POST) 
If an existing Channel entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/channel/{id}"   (HTTP-PUT) 
If an existing Channel entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/channel/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Message columns: 
    - column: ReplyToMessage 
    - column: Channel 
    - column: Content 
    - column: EditedAt 
    - column: CreatedAt 
    - column: AuthorUser 
    - column: IsPinned 
The table should have the title "Messages" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/message/channel/{id}" 
Add a HTML table to the view with the following VoiceSession columns: 
    - column: Channel 
    - column: EndedAt 
    - column: StartedAt 
The table should have the title "VoiceSessions" und the data must be loaded from the server with the following relative URL: 
    "/VoiceSessionService/voicesession/channel/{id}"

2. The MessageView must contain the following fields: 
    - name: AuthorUser   type: UserAccount 
    - name: Channel   type: Channel 
    - name: Content   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: EditedAt   type: DATE 
    - name: IsPinned   type: BOOL 
    - name: ReplyToMessage   type: LONG 
The data source for the [AuthorUser] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
The data source for the [Channel] select control should be loaded from the relative URL: 
    "/UserAccountService/channel"   (HTTP-GET) 
An existing Message entity should be loaded from the relative URL: 
    "/UserAccountService/message/{id}"   (HTTP-GET) 
If a new Message entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/message"   (HTTP-POST) 
If an existing Message entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/message/{id}"   (HTTP-PUT) 
If an existing Message entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/message/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Reaction columns: 
    - column: Message 
    - column: User 
    - column: CreatedAt 
    - column: Emoji 
The table should have the title "Reactions" und the data must be loaded from the server with the following relative URL: 
    "/VoiceSessionService/reaction/message/{id}"

3. The NitroSubscriptionView must contain the following fields: 
    - name: AutoRenews   type: BOOL 
    - name: EndedAt   type: DATE 
    - name: StartedAt   type: DATE 
    - name: SubscriptionPlan   type: SubscriptionPlan 
    - name: User   type: UserAccount 
The data source for the [SubscriptionPlan] select control should be loaded from the relative URL: 
    "/SubscriptionPlanService/subscriptionplan"   (HTTP-GET) 
The data source for the [User] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing NitroSubscription entity should be loaded from the relative URL: 
    "/UserAccountService/nitrosubscription/{id}"   (HTTP-GET) 
If a new NitroSubscription entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/nitrosubscription"   (HTTP-POST) 
If an existing NitroSubscription entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/nitrosubscription/{id}"   (HTTP-PUT) 
If an existing NitroSubscription entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/nitrosubscription/{id}"   (HTTP-DELETE)

4. The ServerView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: Description   type: STRING 
    - name: IsPublic   type: BOOL 
    - name: Name   type: STRING 
    - name: OwnerUser   type: UserAccount 
    - name: PrimaryLanguage   type: STRING 
    - name: Region   type: STRING 
The data source for the [OwnerUser] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing Server entity should be loaded from the relative URL: 
    "/UserAccountService/server/{id}"   (HTTP-GET) 
If a new Server entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/server"   (HTTP-POST) 
If an existing Server entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/server/{id}"   (HTTP-PUT) 
If an existing Server entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/server/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Role columns: 
    - column: Server 
    - column: IsHoisted 
    - column: Name 
    - column: Color 
    - column: IsMentionable 
    - column: Position 
The table should have the title "Roles" und the data must be loaded from the server with the following relative URL: 
    "/RoleService/role/server/{id}" 
Add a HTML table to the view with the following ServerMember columns: 
    - column: IsMuted 
    - column: User 
    - column: IsBanned 
    - column: Server 
    - column: JoinedAt 
    - column: Nickname 
The table should have the title "ServerMembers" und the data must be loaded from the server with the following relative URL: 
    "/ServerMemberService/servermember/server/{id}" 
Add a HTML table to the view with the following Channel columns: 
    - column: Category 
    - column: Position 
    - column: Name 
    - column: UserLimit 
    - column: Type 
    - column: CreatedAt 
    - column: Bitrate 
    - column: IsNsfw 
    - column: Server 
The table should have the title "Channels" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/channel/server/{id}"

5. The UserAccountView must contain the following fields: 
    - name: Country   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: Discriminator   type: STRING 
    - name: Email   type: STRING 
    - name: IsBot   type: BOOL 
    - name: Language   type: STRING 
    - name: Username   type: STRING 
An existing UserAccount entity should be loaded from the relative URL: 
    "/UserAccountService/useraccount/{id}"   (HTTP-GET) 
If a new UserAccount entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-POST) 
If an existing UserAccount entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/useraccount/{id}"   (HTTP-PUT) 
If an existing UserAccount entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/useraccount/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Server columns: 
    - column: PrimaryLanguage 
    - column: CreatedAt 
    - column: IsPublic 
    - column: OwnerUser 
    - column: Region 
    - column: Description 
    - column: Name 
The table should have the title "Servers" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/server/owneruser/{id}" 
Add a HTML table to the view with the following NitroSubscription columns: 
    - column: EndedAt 
    - column: User 
    - column: AutoRenews 
    - column: SubscriptionPlan 
    - column: StartedAt 
The table should have the title "NitroSubscriptions" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/nitrosubscription/user/{id}" 
Add a HTML table to the view with the following Message columns: 
    - column: ReplyToMessage 
    - column: Channel 
    - column: Content 
    - column: EditedAt 
    - column: CreatedAt 
    - column: AuthorUser 
    - column: IsPinned 
The table should have the title "Messages" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/message/authoruser/{id}" 
Add a HTML table to the view with the following ServerMember columns: 
    - column: IsMuted 
    - column: User 
    - column: IsBanned 
    - column: Server 
    - column: JoinedAt 
    - column: Nickname 
The table should have the title "ServerMembers" und the data must be loaded from the server with the following relative URL: 
    "/ServerMemberService/servermember/user/{id}" 
Add a HTML table to the view with the following VoiceParticipant columns: 
    - column: User 
    - column: VoiceSession 
    - column: IsMuted 
    - column: JoinedAt 
    - column: LeftAt 
    - column: IsDeafened 
The table should have the title "VoiceParticipants" und the data must be loaded from the server with the following relative URL: 
    "/VoiceSessionService/voiceparticipant/user/{id}" 
Add a HTML table to the view with the following Reaction columns: 
    - column: Message 
    - column: User 
    - column: CreatedAt 
    - column: Emoji 
The table should have the title "Reactions" und the data must be loaded from the server with the following relative URL: 
    "/VoiceSessionService/reaction/user/{id}"