Overview
Summary
Contact
Donate
Imprint
Prompt for the
RoleApp
Please create a React-JS application for the RoleModule. The application has to offer the following views for the user interface: 1. PermissionView 2. RoleView 3. RolePermissionView 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 PermissionView must contain the following fields: - name: Description type: STRING - name: Name type: STRING An existing Permission entity should be loaded from the relative URL: "/RoleService/permission/{id}" (HTTP-GET) If a new Permission entity has been created, the new entity should be posted to the relative URL: "/RoleService/permission" (HTTP-POST) If an existing Permission entity has been updated, the modified entity should be sent to the relative URL: "/RoleService/permission/{id}" (HTTP-PUT) If an existing Permission entity has to be deleted, the following relative URL should be called: "/RoleService/permission/{id}" (HTTP-DELETE) Add a HTML table to the view with the following RolePermission columns: - column: IsAllowed - column: Permission - column: Role The table should have the title "RolePermissions" und the data must be loaded from the server with the following relative URL: "/RoleService/rolepermission/permission/{id}" 2. The RoleView must contain the following fields: - name: Color type: STRING - name: IsHoisted type: BOOL - name: IsMentionable type: BOOL - name: Name type: STRING - name: Position type: LONG - name: Server type: Server The data source for the [Server] select control should be loaded from the relative URL: "/UserAccountService/server" (HTTP-GET) An existing Role entity should be loaded from the relative URL: "/RoleService/role/{id}" (HTTP-GET) If a new Role entity has been created, the new entity should be posted to the relative URL: "/RoleService/role" (HTTP-POST) If an existing Role entity has been updated, the modified entity should be sent to the relative URL: "/RoleService/role/{id}" (HTTP-PUT) If an existing Role entity has to be deleted, the following relative URL should be called: "/RoleService/role/{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/role/{id}" Add a HTML table to the view with the following RolePermission columns: - column: IsAllowed - column: Permission - column: Role The table should have the title "RolePermissions" und the data must be loaded from the server with the following relative URL: "/RoleService/rolepermission/role/{id}" 3. The RolePermissionView must contain the following fields: - name: IsAllowed type: BOOL - name: Permission type: Permission - name: Role type: Role The data source for the [Role] select control should be loaded from the relative URL: "/RoleService/role" (HTTP-GET) The data source for the [Permission] select control should be loaded from the relative URL: "/RoleService/permission" (HTTP-GET) An existing RolePermission entity should be loaded from the relative URL: "/RoleService/rolepermission/{id}" (HTTP-GET) If a new RolePermission entity has been created, the new entity should be posted to the relative URL: "/RoleService/rolepermission" (HTTP-POST) If an existing RolePermission entity has been updated, the modified entity should be sent to the relative URL: "/RoleService/rolepermission/{id}" (HTTP-PUT) If an existing RolePermission entity has to be deleted, the following relative URL should be called: "/RoleService/rolepermission/{id}" (HTTP-DELETE)
Copy prompt
Overview
Summary
Contact
Donate
Imprint