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.
29 lines
604 B
GraphQL
29 lines
604 B
GraphQL
extend type Mutation {
|
|
createProject(input: NewProject!): Project! @hasRole(roles: [ADMIN], level: TEAM, type: TEAM)
|
|
deleteProject(input: DeleteProject!):
|
|
DeleteProjectPayload! @hasRole(roles: [ADMIN], level: PROJECT, type: PROJECT)
|
|
updateProjectName(input: UpdateProjectName):
|
|
Project! @hasRole(roles: [ADMIN], level: PROJECT, type: PROJECT)
|
|
}
|
|
|
|
input NewProject {
|
|
userID: UUID!
|
|
teamID: UUID!
|
|
name: String!
|
|
}
|
|
|
|
input UpdateProjectName {
|
|
projectID: UUID!
|
|
name: String!
|
|
}
|
|
|
|
input DeleteProject {
|
|
projectID: UUID!
|
|
}
|
|
|
|
type DeleteProjectPayload {
|
|
ok: Boolean!
|
|
project: Project!
|
|
}
|
|
|