Yadciel/taskcafe
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
886b2763ee
taskcafe/internal/graph/schema/schema.gql

152 lines
2.0 KiB
Plaintext
Raw Normal View History

refactor: split resolver into multiple files based on domain
2021-10-26 00:42:57 +02:00
scalar Time
scalar UUID
scalar Upload
enum RoleCode {
owner
admin
member
observer
}
type Role {
code: String!
name: String!
}
type ProfileIcon {
url: String
initials: String
bgColor: String
}
type OwnersList {
projects: [UUID!]!
teams: [UUID!]!
}
type OwnedList {
teams: [Team!]!
projects: [Project!]!
}
type MemberList {
teams: [Team!]!
projects: [Project!]!
}
type Organization {
id: ID!
name: String!
}
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
enum ShareStatus {
INVITED
JOINED
}
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
enum RoleLevel {
ADMIN
MEMBER
}
enum ActionLevel {
ORG
TEAM
PROJECT
}
enum ObjectType {
ORG
TEAM
PROJECT
TASK
fix: member permissions now works correctly
2020-09-20 00:26:02 +02:00
TASK_GROUP
TASK_CHECKLIST
TASK_CHECKLIST_ITEM
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
}
directive @hasRole(roles: [RoleLevel!]!, level: ActionLevel!, type: ObjectType!) on FIELD_DEFINITION
refactor: split resolver into multiple files based on domain
2021-10-26 00:42:57 +02:00
feat: projects can be set to public
2021-05-01 05:55:37 +02:00
directive @requiresUser on FIELD_DEFINITION
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
type Query {
organizations: [Organization!]!
users: [UserAccount!]!
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
invitedUsers: [InvitedUserAccount!]!
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
findUser(input: FindUser!): UserAccount!
projects(input: ProjectsFilter): [Project!]!
teams: [Team!]!
feat: change url structure to use short ids instead of full uuids
2021-11-04 19:36:46 +01:00
findTeam(input: FindTeam!): Team!
feat: add my tasks list view
2020-12-31 03:56:59 +01:00
myTasks(input: MyTasks!): MyTasksPayload!
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
labelColors: [LabelColor!]!
taskGroups: [TaskGroup!]!
feat: projects can be set to public
2021-05-01 05:55:37 +02:00
me: MePayload
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
}
feat: add my tasks list view
2020-12-31 03:56:59 +01:00
refactor(magefile): update schema generator to use 0644 file permissions
2021-10-26 21:42:04 +02:00
type Subscription
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
type Mutation
feat: add my tasks list view
2020-12-31 03:56:59 +01:00
enum MyTasksStatus {
ALL
INCOMPLETE
COMPLETE_ALL
COMPLETE_TODAY
COMPLETE_YESTERDAY
COMPLETE_ONE_WEEK
COMPLETE_TWO_WEEK
COMPLETE_THREE_WEEK
}
enum MyTasksSort {
NONE
PROJECT
DUE_DATE
}
input MyTasks {
status: MyTasksStatus!
sort: MyTasksSort!
}
type ProjectTaskMapping {
projectID: UUID!
taskID: UUID!
}
type MyTasksPayload {
tasks: [Task!]!
projects: [ProjectTaskMapping!]!
}
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
type TeamRole {
teamID: UUID!
roleCode: RoleCode!
}
type ProjectRole {
projectID: UUID!
roleCode: RoleCode!
}
type MePayload {
user: UserAccount!
refactor: replace refresh & access token with auth token only changes authentication to no longer use a refresh token & access token for accessing protected endpoints. Instead only an auth token is used. Before the login flow was: Login -> get refresh (stored as HttpOnly cookie) + access token (stored in memory) -> protected endpoint request (attach access token as Authorization header) -> access token expires in 15 minutes, so use refresh token to obtain new one when that happens now it looks like this: Login -> get auth token (stored as HttpOnly cookie) -> make protected endpont request (token sent) the reasoning for using the refresh + access token was to reduce DB calls, but in the end I don't think its worth the hassle.
2021-04-29 04:32:19 +02:00
organization: RoleCode
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
teamRoles: [TeamRole!]!
projectRoles: [ProjectRole!]!
}
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
input ProjectsFilter {
teamID: UUID
}
input FindUser {
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 FindTeam {
teamID: UUID!
}
Reference in New Issue Copy Permalink