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

Introduce "warning" policy; change no-var to a warning #1586

Merged
merged 6 commits into from Oct 31, 2020
Merged

Conversation

feross
Copy link
Member

@feross feross commented Oct 30, 2020

What is the purpose of this pull request? (put an "X" next to item)

[ ] Documentation update
[ ] Bug fix
[x] New feature
[ ] Other, please explain:

What changes did you make? (Give an overview)

Explain the difference between errors and warnings in the FAQ. Prep for releasing 16.0.1.

Which issue (if any) does this pull request address?

#633

Is there anything you'd like reviewers to focus on?

  • Is the explanation about the difference between errors and warnings clear enough?
  • Does the policy make sense?

@feross
Copy link
Member Author

feross commented Oct 30, 2020

@standard/team - can you take a look at this?

Copy link

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@mafintosh
Copy link
Contributor

I think warnings are a great way to check if a change has impact on newly written modules or existing ones with a high velocity of changes without having to worry about breakage to existing “finished” ones so big 👍 from me

@feross feross merged commit 447ddae into master Oct 31, 2020
@feross feross deleted the warnings branch October 31, 2020 02:58
@feross
Copy link
Member Author

feross commented Oct 31, 2020

Thanks for the reviews, @mcollina and @mafintosh!

@feross
Copy link
Member Author

feross commented Oct 31, 2020

Released as 16.0.1

@LinusU
Copy link
Member

LinusU commented Nov 2, 2020

Awesome work getting this out quickly! 🌟

@feross
Copy link
Member Author

feross commented Nov 11, 2020

Thanks @LinusU ❤️

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

4 participants