-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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 3rd option to lintOnSave
to support 'default' behaviour (fix #3552)
#3572
Conversation
previous singluar flag 'error'
lintOnSave
to support 'default' behaviour
lintOnSave
to support 'default' behaviourlintOnSave
to support 'default' behaviour (fix #3552)
Oh i just found some mistakes in the docs changes. Don't merge this yet! |
add missing 'warning' value.
Should be good now. |
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.
Did you accidentally turn on some editor plugin to aggressively format the code?
I saw several unnecessary code style changes:
- extra spaces before
:::
- extra trailing commas in the code examples
- missing indentations in
packages/@vue/cli-plugin-eslint/index.js
etc.
This also happens in #3523
Yeah sorry, I'll undo those. |
Thanks for cleaning up the remaining formatting issue :/ I've ensured that my editor won't do that again. |
BREAKING CHANGE: See vuejs#3572
BREAKING CHANGE: See #3572
BREAKING CHANGE: See vuejs/vue-cli#3572
BREAKING CHANGE: See vuejs/vue-cli#3572
Right now, when enabled, lintOnSave either emits everything as warnings (
true
), or everything as errors ('error'
).This PR adds a another option,
'default'
, which will do what most people would expect: emit errors as errors, and warnings as warnings.Explanation of new set of options:
"default"
: emit warnings and warnings and errors as errors (the new behaviour)"warning"
: emit everything as warnings (avoid errors to pop up in overlay during development)"error"
: emit everything as errorstrue
: same as"warning"
(also same as current behavior so it doesn't have to be breaking, can be deprecated in next major)close #3552