e64f6f8569
enforces user admin role requirement for - creating / deleting / setting role for organization users - creating / deleting / setting role for project users - updating project name - deleting project hides action elements based on role for - admin console - team settings if team is only visible through project membership - add project tile if not team admin - project name text editor if not team / project admin - add redirect from team page if settings only visible through project membership - add redirect from admin console if not org admin role enforcement is handled on the api side through a custom GraphQL directive `hasRole`. on the client side, role information is fetched in the TopNavbar's `me` query and stored in the `UserContext`. there is a custom hook, `useCurrentUser`, that provides a user object with two functions, `isVisibile` & `isAdmin` which is used to check roles in order to render/hide relevant UI elements.
37 lines
888 B
GraphQL
37 lines
888 B
GraphQL
extend type Mutation {
|
|
createTaskGroup(input: NewTaskGroup!):
|
|
TaskGroup! @hasRole(roles: [ADMIN], level: PROJECT, type: PROJECT)
|
|
updateTaskGroupLocation(input: NewTaskGroupLocation!):
|
|
TaskGroup! @hasRole(roles: [ADMIN], level: PROJECT, type: PROJECT)
|
|
updateTaskGroupName(input: UpdateTaskGroupName!):
|
|
TaskGroup! @hasRole(roles: [ADMIN], level: PROJECT, type: PROJECT)
|
|
deleteTaskGroup(input: DeleteTaskGroupInput!):
|
|
DeleteTaskGroupPayload! @hasRole(roles: [ADMIN], level: PROJECT, type: PROJECT)
|
|
}
|
|
|
|
input NewTaskGroupLocation {
|
|
taskGroupID: UUID!
|
|
position: Float!
|
|
}
|
|
|
|
input UpdateTaskGroupName {
|
|
taskGroupID: UUID!
|
|
name: String!
|
|
}
|
|
|
|
input DeleteTaskGroupInput {
|
|
taskGroupID: UUID!
|
|
}
|
|
|
|
type DeleteTaskGroupPayload {
|
|
ok: Boolean!
|
|
affectedRows: Int!
|
|
taskGroup: TaskGroup!
|
|
}
|
|
|
|
input NewTaskGroup {
|
|
projectID: String!
|
|
name: String!
|
|
position: Float!
|
|
}
|