-
Notifications
You must be signed in to change notification settings - Fork 636
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
Enable explicit disabling of default plugins #2019
Labels
TAG: new feature
New user-facing feature
Comments
This was referenced Dec 23, 2017
Not sure this is critical, as the default plugin list for custom builds will be set specifically for those custom builds. |
I don't remember why I set it to critical. |
fixed in #5637 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
In latest changes in #2013, we re-enable default plugins at a version change.
This could be annoying for users who have explicitly disabled a plugin for a reason, so it would be helpful to explicitly blacklist a default plugin to protect against this behaviour.
Additionally, as suggested in #17 let's migrate from
json
toini
The text was updated successfully, but these errors were encountered: