-
Notifications
You must be signed in to change notification settings - Fork 2
Remove role check #1929
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
Remove role check #1929
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
... and 5 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
|
Currently the behavior is not the same when submitting a directory entry vs creating/editing one as manager. The submission does not depend on the role Added a test and removed the role check for managers. |
Daverball
left a comment
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.
I'm not convinced that this is worth changing. It does make sense to me that publication control is something that would usually be limited to admins (and potentially editors), unless it was explicitly enabled for everyone.
I'm a little worried that we're breaking a behavior our customers have been relying on, so I would prefer to drop this change, until we're actually sure it's harmless. Looking at the git blame of this line I'm seeing commit 2e32b23 explicitly added this check on purpose, so I'm assuming it's working as intended. I'm fine with widening this feature from admins to editors, but I don't think I'm fine with removing it altogether.
|
I understand your arguments. Background of my change was a sentry issue if I remember correctly, but I didn't note it down... |
Directories: Publication settings for directory entries independent of role
Same as for submitted directory entries
TYPE: Feature
LINK: None