Yadciel/taskcafe
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
refactor/consistent-themes
taskcafe/internal/graph/schema/user.gql

101 lines
2.0 KiB
Plaintext
Raw Permalink Normal View History

cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
extend type Mutation {
createRefreshToken(input: NewRefreshToken!): RefreshToken!
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
createUserAccount(input: NewUserAccount!):
UserAccount! @hasRole(roles: [ADMIN], level: ORG, type: ORG)
deleteUserAccount(input: DeleteUserAccount!):
DeleteUserAccountPayload! @hasRole(roles: [ADMIN], level: ORG, type: ORG)
feat: redesign project sharing & initial registration redesigned the project sharing popup to be a multi select dropdown that populates the options by using the input as a fuzzy search filter on the current users & invited users. users can now also be directly invited by email from the project share window. if invited this way, then the user will receive an email that sends them to a registration page, then a confirmation page. the initial registration was always redone so that it uses a similar system to the above in that it now will accept the first registered user if there are no other accounts (besides 'system').
2020-10-21 01:52:09 +02:00
deleteInvitedUserAccount(input: DeleteInvitedUserAccount!):
DeleteInvitedUserAccountPayload! @hasRole(roles: [ADMIN], level: ORG, type: ORG)
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
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
logoutUser(input: LogoutUser!): Boolean!
clearProfileAvatar: UserAccount!
chore: project cleanup and bugfixes
2020-07-12 09:06:11 +02:00
feature: add web & migrate commands
2020-07-16 01:20:08 +02:00
updateUserPassword(input: UpdateUserPassword!): UpdateUserPasswordPayload!
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
updateUserRole(input: UpdateUserRole!):
UpdateUserRolePayload! @hasRole(roles: [ADMIN], level: ORG, type: ORG)
feat: add user profile settings tab
2020-09-11 20:54:43 +02:00
updateUserInfo(input: UpdateUserInfo!):
UpdateUserInfoPayload! @hasRole(roles: [ADMIN], level: ORG, type: ORG)
}
feat: redesign project sharing & initial registration redesigned the project sharing popup to be a multi select dropdown that populates the options by using the input as a fuzzy search filter on the current users & invited users. users can now also be directly invited by email from the project share window. if invited this way, then the user will receive an email that sends them to a registration page, then a confirmation page. the initial registration was always redone so that it uses a similar system to the above in that it now will accept the first registered user if there are no other accounts (besides 'system').
2020-10-21 01:52:09 +02:00
extend type Query {
searchMembers(input: MemberSearchFilter!): [MemberSearchResult!]!
}
input DeleteInvitedUserAccount {
invitedUserID: UUID!
}
type DeleteInvitedUserAccountPayload {
invitedUser: InvitedUserAccount!
}
input MemberSearchFilter {
searchFilter: String!
projectID: UUID
}
type MemberSearchResult {
similarity: Int!
id: String!
user: UserAccount
status: ShareStatus!
}
feat: add user profile settings tab
2020-09-11 20:54:43 +02:00
type UpdateUserInfoPayload {
user: UserAccount!
}
input UpdateUserInfo {
name: String!
initials: String!
email: String!
bio: String!
chore: project cleanup and bugfixes
2020-07-12 09:06:11 +02:00
}
feature: add web & migrate commands
2020-07-16 01:20:08 +02:00
input UpdateUserPassword {
userID: UUID!
password: String!
}
type UpdateUserPasswordPayload {
ok: Boolean!
user: UserAccount!
}
chore: project cleanup and bugfixes
2020-07-12 09:06:11 +02:00
input UpdateUserRole {
userID: UUID!
roleCode: RoleCode!
}
type UpdateUserRolePayload {
user: UserAccount!
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
}
input NewRefreshToken {
fix: member permissions now works correctly
2020-09-20 00:26:02 +02:00
userID: UUID!
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
}
input NewUserAccount {
username: String!
email: String!
fullName: String!
initials: String!
password: String!
roleCode: String!
}
input LogoutUser {
fix: member permissions now works correctly
2020-09-20 00:26:02 +02:00
userID: UUID!
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
}
input DeleteUserAccount {
userID: UUID!
feature: fix user admin related bugs
2020-07-18 04:55:38 +02:00
newOwnerID: UUID
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
}
type DeleteUserAccountPayload {
ok: Boolean!
userAccount: UserAccount!
}
Reference in New Issue Copy Permalink