Skip to content
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

Merged
merged 8 commits into from
Apr 1, 2019

Conversation

LinusBorg
Copy link
Member

@LinusBorg LinusBorg commented Mar 4, 2019

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 errors
  • true: same as "warning" (also same as current behavior so it doesn't have to be breaking, can be deprecated in next major)

close #3552

@LinusBorg LinusBorg changed the title refactor: fix flag names to align with Add 3rd option to lintOnSave to support 'default' behaviour Mar 4, 2019
@LinusBorg LinusBorg changed the title Add 3rd option to lintOnSave to support 'default' behaviour Add 3rd option to lintOnSave to support 'default' behaviour (fix #3552) Mar 4, 2019
@LinusBorg
Copy link
Member Author

Oh i just found some mistakes in the docs changes.

Don't merge this yet!

@LinusBorg LinusBorg self-assigned this Mar 4, 2019
add missing 'warning' value.
@LinusBorg
Copy link
Member Author

Should be good now.

@LinusBorg LinusBorg removed their assignment Mar 5, 2019
Copy link
Member

@sodatea sodatea left a 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

@LinusBorg
Copy link
Member Author

Yeah sorry, I'll undo those.

@LinusBorg LinusBorg self-assigned this Mar 6, 2019
@LinusBorg LinusBorg removed their assignment Mar 8, 2019
@sodatea sodatea changed the base branch from dev to next-minor April 1, 2019 10:07
@sodatea sodatea merged commit a6d3166 into next-minor Apr 1, 2019
@LinusBorg
Copy link
Member Author

Thanks for cleaning up the remaining formatting issue :/

I've ensured that my editor won't do that again.

@LinusBorg LinusBorg deleted the issue-3552 branch May 3, 2019 12:24
sodatea added a commit to sodatea/vue-cli that referenced this pull request May 10, 2019
sodatea added a commit that referenced this pull request May 14, 2019
ZanderOlidan pushed a commit to ZanderOlidan/vue-cli-service-chalkfix that referenced this pull request Feb 5, 2024
ZanderOlidan pushed a commit to ZanderOlidan/vue-cli-service-chalkfix that referenced this pull request Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants