-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Add option to propagate permissions to sub collections #8233
Conversation
…abase into propagate-collections-perms
Good point, fixed. |
…abase into propagate-collections-perms
450f22e
to
faeac0f
Compare
Looks like this is ready for review from @salsakran and @kdoh. Let's merge this puppy. |
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.
seems to work well from my manual testing of it
I can live with the toggle, though it does not fill me with aesthetic glee.
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.
👍 for the propagation itself.
Not sure I'm loving the overall flow of the interaction for this though. The mixture of select items that immediately close the select and set your choice and then a toggle below just feels a little messy. For lack of a better term it feels like I could use more of a moment of pause to understand what going on if I'm potentially going to affect a bunch of items I can't see here (especially since we're defaulting to on).
Also curious if there's a reason why we went for a toggle vs a checkbox here. Small distinction but to me the toggle has more of a global implication whereas a checkbox feels possibly more appropriate on a per "instance" setting like this.
Cool, thanks for the feedback. I could go either way with a checkbox vs. a toggle. The reason that I opted for this defaulting on and it being handled by a toggle instead of a separate confirmation was:
I.e., would you want to have to click this every time? |
I think my reaction to it was more about the context in which things are happening than the defaulting to on (which makes sense). Just feels like the put these options in a popover strategy is starting to get a little messy. Anyhoo, as reflected by the fact this is merged I think it's an overall net win. |
Also resolves #8205