-
Notifications
You must be signed in to change notification settings - Fork 27
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
Modified scope handling. #150
Conversation
Maybe we can look at the effect of having and not having |
Special rules like that seem a generally bad idea - Why was |
We shall ignore the Codacy issue as |
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.
As discussed we decided that all in all !important
wasn't that bad in the scheme of things.
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 feel like these changes could do with more documentation on them, either in the commit message or PR.
As discussed yesterday, @ineilson please do add a second commit that removes the now unused code for reading the reserved scopes from a local config and changes any relevant comments. |
I have also "ignored" the codacy issue: https://app.codacy.com/app/gocdb/gocdb/issues/ignored because #wontfix |
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.
Thanks Ian, I've added this PR to the 5.8.0 milestone, so will leave it un-merged till then.
8fe5389
Finger (or brain) trouble, accidentally force pushed outdated scopes branch. Apologies. |
edit/success screens
Removed unused method for loading reserved scopes from local_config.xml and adjust some comments.
I've rebased this and checked nothing got lost or broken during the process. |
Closes #99.
Moves reserved scopes definition out of the local config xml and into the scopes table in the database as a 'reserved' boolean associated with each scope entry. Addition of consequent changes to the interface to allow those with admin privileges to set/unset the reserved state flag on a scope at creation and if editting.
Would prefer not to use '!important' in web_portal.css which serves to left-align the 'reserved' checkbox correctly under the text entry boxes for name and description in the add/edit scope dialogues.