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

230 lines
3.2 KiB
Plaintext
Raw Normal View History

cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
scalar Time
scalar UUID
scalar Upload
enum RoleCode {
owner
admin
member
observer
}
type ProjectLabel {
id: ID!
createdDate: Time!
labelColor: LabelColor!
name: String
}
type LabelColor {
id: ID!
name: String!
position: Float!
colorHex: String!
}
type TaskLabel {
id: ID!
projectLabel: ProjectLabel!
assignedDate: Time!
}
type ProfileIcon {
url: String
initials: String
bgColor: String
}
chore: project cleanup and bugfixes
2020-07-12 09:06:11 +02:00
type OwnersList {
projects: [UUID!]!
teams: [UUID!]!
}
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
type Member {
id: ID!
role: Role!
fullName: String!
username: String!
profileIcon: ProfileIcon!
feature: add user project count to Admin component
2020-07-18 02:40:05 +02:00
owned: OwnedList!
member: MemberList!
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
}
type Role {
code: String!
name: String!
}
feature: add user project count to Admin component
2020-07-18 02:40:05 +02:00
type OwnedList {
teams: [Team!]!
projects: [Project!]!
}
type MemberList {
teams: [Team!]!
projects: [Project!]!
}
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
type UserAccount {
id: ID!
email: String!
createdAt: Time!
fullName: String!
initials: String!
feat: add user profile settings tab
2020-09-11 20:54:43 +02:00
bio: String!
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
role: Role!
username: String!
profileIcon: ProfileIcon!
feature: add user project count to Admin component
2020-07-18 02:40:05 +02:00
owned: OwnedList!
member: MemberList!
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
}
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
type InvitedUserAccount {
id: ID!
email: String!
invitedOn: Time!
member: MemberList!
}
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
type Team {
id: ID!
createdAt: Time!
name: String!
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
permission: TeamPermission!
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
members: [Member!]!
}
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
type InvitedMember {
email: String!
invitedOn: Time!
}
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
type TeamPermission {
team: RoleCode!
org: RoleCode!
}
type ProjectPermission {
team: RoleCode!
project: RoleCode!
org: RoleCode!
}
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
type Project {
id: ID!
createdAt: Time!
name: String!
feat: add personal projects personal projects are projects that have no team. they can only seen by the project members (one of which is whoever first creates the project).
2020-09-20 03:20:36 +02:00
team: Team
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
taskGroups: [TaskGroup!]!
members: [Member!]!
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
invitedMembers: [InvitedMember!]!
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
permission: ProjectPermission!
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
labels: [ProjectLabel!]!
}
type TaskGroup {
id: ID!
projectID: String!
createdAt: Time!
name: String!
position: Float!
tasks: [Task!]!
}
type ChecklistBadge {
complete: Int!
total: Int!
}
type TaskBadges {
checklist: ChecklistBadge
}
feat: add task activity
2020-12-19 03:34:35 +01:00
type CausedBy {
id: ID!
fullName: String!
profileIcon: ProfileIcon
}
type TaskActivityData {
name: String!
value: String!
}
enum ActivityType {
TASK_ADDED
TASK_MOVED
TASK_MARKED_COMPLETE
TASK_MARKED_INCOMPLETE
TASK_DUE_DATE_CHANGED
TASK_DUE_DATE_ADDED
TASK_DUE_DATE_REMOVED
TASK_CHECKLIST_CHANGED
TASK_CHECKLIST_ADDED
TASK_CHECKLIST_REMOVED
}
type TaskActivity {
id: ID!
type: ActivityType!
data: [TaskActivityData!]!
causedBy: CausedBy!
createdAt: Time!
}
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
type Task {
id: ID!
taskGroup: TaskGroup!
createdAt: Time!
name: String!
position: Float!
description: String
dueDate: Time
feat: redesign task due date manager
2021-01-01 21:51:40 +01:00
hasTime: Boolean!
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
complete: Boolean!
feat: add task sorting & filtering adds filtering by task status (completion date, incomplete, completion) adds filtering by task metadata (task name, labels, members, due date) adds sorting by task name, labels, members, and due date
2020-08-28 01:57:23 +02:00
completedAt: Time
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
assigned: [Member!]!
labels: [TaskLabel!]!
checklists: [TaskChecklist!]!
badges: TaskBadges!
feat: add task activity
2020-12-19 03:34:35 +01:00
activity: [TaskActivity!]!
comments: [TaskComment!]!
}
type CreatedBy {
id: ID!
fullName: String!
profileIcon: ProfileIcon!
}
type TaskComment {
id: ID!
createdAt: Time!
updatedAt: Time
message: String!
createdBy: CreatedBy!
pinned: Boolean!
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
}
type Organization {
id: ID!
name: String!
}
type TaskChecklistItem {
id: ID!
name: String!
taskChecklistID: UUID!
complete: Boolean!
position: Float!
dueDate: Time!
}
type TaskChecklist {
id: ID!
name: String!
position: Float!
items: [TaskChecklistItem!]!
}
Reference in New Issue Copy Permalink