-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updates to collaboration screen #321
Conversation
✅ Deploy Preview for recogito-cloud-staging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for vico-design ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! (I added the DE label.)
src/backend/crud/projects.ts
Outdated
@@ -8,7 +8,7 @@ import type { | |||
import type { Response } from '@backend/Types'; | |||
import { getUser } from '@backend/auth'; | |||
import type { ApiPostInviteUserToProject } from 'src/Types'; | |||
import type { InviteListEntry } from '@apps/project-collaboration/InviteListOfUsers/InviteListOfUsers'; | |||
import type { InviteListEntry } from '@apps/project-collaboration/InviteListOfUsersDialog/InviteListOfUsers'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That file doesn't seem to exist any more. (Should be InviteListOfUsersDialog
?)
In general, I think I'd bundle the types with the backend code, and then import from there into the UI code, rather than vice versa. But that's really just a matter of taste I guess & no strong opinion either way.
…gito/recogito-client into lwj/project-team-page-fixes
Summary