Overview
Summary
Contact
Donate
Imprint
Prompt for the
ServerMemberApp
Please create a React-JS application for the ServerMemberModule. The application has to offer the following views for the user interface: 1. ExtremistGroupView 2. MemberRoleView 3. ServerMemberView The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 3 views are defined below. 1. The ExtremistGroupView must contain the following fields: - name: ActiveFrom type: DATE - name: ActiveTo type: DATE - name: Country type: STRING - name: Description type: STRING - name: Ideology type: STRING - name: Name type: STRING - name: UsesDiscord type: BOOL An existing ExtremistGroup entity should be loaded from the relative URL: "/ServerMemberService/extremistgroup/{id}" (HTTP-GET) If a new ExtremistGroup entity has been created, the new entity should be posted to the relative URL: "/ServerMemberService/extremistgroup" (HTTP-POST) If an existing ExtremistGroup entity has been updated, the modified entity should be sent to the relative URL: "/ServerMemberService/extremistgroup/{id}" (HTTP-PUT) If an existing ExtremistGroup entity has to be deleted, the following relative URL should be called: "/ServerMemberService/extremistgroup/{id}" (HTTP-DELETE) 2. The MemberRoleView must contain the following fields: - name: AssignedAt type: DATE - name: Role type: Role - name: ServerMember type: ServerMember The data source for the [Role] select control should be loaded from the relative URL: "/RoleService/role" (HTTP-GET) The data source for the [ServerMember] select control should be loaded from the relative URL: "/ServerMemberService/servermember" (HTTP-GET) An existing MemberRole entity should be loaded from the relative URL: "/ServerMemberService/memberrole/{id}" (HTTP-GET) If a new MemberRole entity has been created, the new entity should be posted to the relative URL: "/ServerMemberService/memberrole" (HTTP-POST) If an existing MemberRole entity has been updated, the modified entity should be sent to the relative URL: "/ServerMemberService/memberrole/{id}" (HTTP-PUT) If an existing MemberRole entity has to be deleted, the following relative URL should be called: "/ServerMemberService/memberrole/{id}" (HTTP-DELETE) 3. The ServerMemberView must contain the following fields: - name: IsBanned type: BOOL - name: IsMuted type: BOOL - name: JoinedAt type: DATE - name: Nickname type: STRING - name: Server type: Server - 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 [Server] select control should be loaded from the relative URL: "/UserAccountService/server" (HTTP-GET) An existing ServerMember entity should be loaded from the relative URL: "/ServerMemberService/servermember/{id}" (HTTP-GET) If a new ServerMember entity has been created, the new entity should be posted to the relative URL: "/ServerMemberService/servermember" (HTTP-POST) If an existing ServerMember entity has been updated, the modified entity should be sent to the relative URL: "/ServerMemberService/servermember/{id}" (HTTP-PUT) If an existing ServerMember entity has to be deleted, the following relative URL should be called: "/ServerMemberService/servermember/{id}" (HTTP-DELETE) Add a HTML table to the view with the following MemberRole columns: - column: ServerMember - column: Role - column: AssignedAt The table should have the title "MemberRoles" und the data must be loaded from the server with the following relative URL: "/ServerMemberService/memberrole/servermember/{id}"
Copy prompt
Overview
Summary
Contact
Donate
Imprint