-
Notifications
You must be signed in to change notification settings - Fork 181
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
feat(projects): filter projects, that are not available under sso #3585
Conversation
…gergo/filterSsoProtectedProjects
…systems/speckle-server into gergo/filterSsoProtectedProjects
@fabis94 could you double check, that the (Stream|Project)Collection -> User(Stream|Project)Collection changes are not breaking anything on the frontend / type system. I've tested with FE2, DUI3 and DUI2 things were working, but i'd like your stamp on this too. |
// a little escape hatch for admins to look into users streams | ||
// const forOtherUser = parent.id !== ctx.userId | ||
const isAdmin = adminOverrideEnabled() && ctx.role === Roles.Server.Admin | ||
const forOtherUser = !isAdmin |
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.
Is this correct? Only show other user's streams if not an admin? Surely it's the inverse? @gjedlicska
the CI's failing, you probably have to merge in main |
…systems/speckle-server into gergo/filterSsoProtectedProjects
Description & motivation
Changes:
To-do before merge:
Screenshots:
Validation of changes:
Checklist:
References