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
Conversation
@standard/team - can you take a look at this? |
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.
lgtm
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 |
Thanks for the reviews, @mcollina and @mafintosh! |
Released as 16.0.1 |
Awesome work getting this out quickly! 🌟 |
Thanks @LinusU ❤️ |
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?