taskcafe/internal/graph/schema/project_member.gql

extend type Mutation {
  inviteProjectMembers(input: InviteProjectMembers!):
    InviteProjectMembersPayload! @hasRole(roles: [ADMIN], level: PROJECT, type: PROJECT)
  deleteProjectMember(input: DeleteProjectMember!):
    DeleteProjectMemberPayload! @hasRole(roles: [ADMIN], level: PROJECT, type: PROJECT)
  updateProjectMemberRole(input: UpdateProjectMemberRole!):
    UpdateProjectMemberRolePayload! @hasRole(roles: [ADMIN], level: PROJECT, type: PROJECT)
}

input MemberInvite {
  userID: UUID
  email: String
}

input InviteProjectMembers {
  projectID: UUID!
  members: [MemberInvite!]!
}

type InviteProjectMembersPayload {
  ok: Boolean!
  projectID: UUID!
  members: [Member!]!
}

input DeleteProjectMember {
  projectID: UUID!
  userID: UUID!
}

type DeleteProjectMemberPayload {
  ok: Boolean!
  member: Member!
  projectID: UUID!
}

input UpdateProjectMemberRole {
  projectID: UUID!
  userID: UUID!
  roleCode: RoleCode!
}

type UpdateProjectMemberRolePayload {
  ok: Boolean!
  member: Member!
}
cleanup: refactor api architecture & add user roles 2020-07-05 01:02:57 +02:00			`extend type Mutation {`
feat: redesign project invite popup 2020-10-14 23:52:32 +02:00			`inviteProjectMembers(input: InviteProjectMembers!):`
			`InviteProjectMembersPayload! @hasRole(roles: [ADMIN], level: PROJECT, type: PROJECT)`
feat: enforce user roles 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. 2020-08-01 03:01:14 +02:00			`deleteProjectMember(input: DeleteProjectMember!):`
			`DeleteProjectMemberPayload! @hasRole(roles: [ADMIN], level: PROJECT, type: PROJECT)`
			`updateProjectMemberRole(input: UpdateProjectMemberRole!):`
			`UpdateProjectMemberRolePayload! @hasRole(roles: [ADMIN], level: PROJECT, type: PROJECT)`
cleanup: refactor api architecture & add user roles 2020-07-05 01:02:57 +02:00			`}`

feat: redesign project invite popup 2020-10-14 23:52:32 +02:00			`input MemberInvite {`
feat: redesign project sharing 2020-09-29 23:01:52 +02:00			`userID: UUID`
			`email: String`
cleanup: refactor api architecture & add user roles 2020-07-05 01:02:57 +02:00			`}`

feat: redesign project invite popup 2020-10-14 23:52:32 +02:00			`input InviteProjectMembers {`
			`projectID: UUID!`
			`members: [MemberInvite!]!`
			`}`

			`type InviteProjectMembersPayload {`
cleanup: refactor api architecture & add user roles 2020-07-05 01:02:57 +02:00			`ok: Boolean!`
feat: redesign project invite popup 2020-10-14 23:52:32 +02:00			`projectID: UUID!`
			`members: [Member!]!`
cleanup: refactor api architecture & add user roles 2020-07-05 01:02:57 +02:00			`}`

			`input DeleteProjectMember {`
			`projectID: UUID!`
			`userID: UUID!`
			`}`

			`type DeleteProjectMemberPayload {`
			`ok: Boolean!`
			`member: Member!`
			`projectID: UUID!`
			`}`

			`input UpdateProjectMemberRole {`
			`projectID: UUID!`
			`userID: UUID!`
			`roleCode: RoleCode!`
			`}`

			`type UpdateProjectMemberRolePayload {`
			`ok: Boolean!`
			`member: Member!`
			`}`