Prompt for the VoiceSessionApp

Please create a React-JS application for the VoiceSessionModule. The application  has to offer the following views for the user interface: 
    1. DocumentLeakView 
    2. ReactionView 
    3. VoiceParticipantView 
    4. VoiceSessionView 
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 DocumentLeakView must contain the following fields: 
    - name: Description   type: STRING 
    - name: EndDate   type: DATE 
    - name: Name   type: STRING 
    - name: RelatedConflict   type: STRING 
    - name: SourcePlatform   type: STRING 
    - name: StartDate   type: DATE 
An existing DocumentLeak entity should be loaded from the relative URL: 
    "/VoiceSessionService/documentleak/{id}"   (HTTP-GET) 
If a new DocumentLeak entity has been created, the new entity should be posted to the relative URL: 
    "/VoiceSessionService/documentleak"   (HTTP-POST) 
If an existing DocumentLeak entity has been updated, the modified entity should be sent to the relative URL: 
    "/VoiceSessionService/documentleak/{id}"   (HTTP-PUT) 
If an existing DocumentLeak entity has to be deleted, the following relative URL should be called: 
    "/VoiceSessionService/documentleak/{id}"   (HTTP-DELETE)

2. The ReactionView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: Emoji   type: STRING 
    - name: Message   type: Message 
    - name: User   type: UserAccount 
The data source for the [User] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
The data source for the [Message] select control should be loaded from the relative URL: 
    "/UserAccountService/message"   (HTTP-GET) 
An existing Reaction entity should be loaded from the relative URL: 
    "/VoiceSessionService/reaction/{id}"   (HTTP-GET) 
If a new Reaction entity has been created, the new entity should be posted to the relative URL: 
    "/VoiceSessionService/reaction"   (HTTP-POST) 
If an existing Reaction entity has been updated, the modified entity should be sent to the relative URL: 
    "/VoiceSessionService/reaction/{id}"   (HTTP-PUT) 
If an existing Reaction entity has to be deleted, the following relative URL should be called: 
    "/VoiceSessionService/reaction/{id}"   (HTTP-DELETE)

3. The VoiceParticipantView must contain the following fields: 
    - name: IsDeafened   type: BOOL 
    - name: IsMuted   type: BOOL 
    - name: JoinedAt   type: DATE 
    - name: LeftAt   type: DATE 
    - name: User   type: UserAccount 
    - name: VoiceSession   type: VoiceSession 
The data source for the [User] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
The data source for the [VoiceSession] select control should be loaded from the relative URL: 
    "/VoiceSessionService/voicesession"   (HTTP-GET) 
An existing VoiceParticipant entity should be loaded from the relative URL: 
    "/VoiceSessionService/voiceparticipant/{id}"   (HTTP-GET) 
If a new VoiceParticipant entity has been created, the new entity should be posted to the relative URL: 
    "/VoiceSessionService/voiceparticipant"   (HTTP-POST) 
If an existing VoiceParticipant entity has been updated, the modified entity should be sent to the relative URL: 
    "/VoiceSessionService/voiceparticipant/{id}"   (HTTP-PUT) 
If an existing VoiceParticipant entity has to be deleted, the following relative URL should be called: 
    "/VoiceSessionService/voiceparticipant/{id}"   (HTTP-DELETE)

4. The VoiceSessionView must contain the following fields: 
    - name: Channel   type: Channel 
    - name: EndedAt   type: DATE 
    - name: StartedAt   type: DATE 
The data source for the [Channel] select control should be loaded from the relative URL: 
    "/UserAccountService/channel"   (HTTP-GET) 
An existing VoiceSession entity should be loaded from the relative URL: 
    "/VoiceSessionService/voicesession/{id}"   (HTTP-GET) 
If a new VoiceSession entity has been created, the new entity should be posted to the relative URL: 
    "/VoiceSessionService/voicesession"   (HTTP-POST) 
If an existing VoiceSession entity has been updated, the modified entity should be sent to the relative URL: 
    "/VoiceSessionService/voicesession/{id}"   (HTTP-PUT) 
If an existing VoiceSession entity has to be deleted, the following relative URL should be called: 
    "/VoiceSessionService/voicesession/{id}"   (HTTP-DELETE) 
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/voicesession/{id}"