-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
recommended
shared config
#402
Milestone
Comments
benmosher
added a commit
that referenced
this issue
Jul 7, 2016
benmosher
added a commit
that referenced
this issue
Jul 7, 2016
@jfmengels would love your feedback on what I put together for this |
I left some comments in the commit. I'd be happy to discuss it more if you want to. Either in a new issue or in the commit. |
This was referenced Apr 15, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seems to be a common pattern amongst plugins.
Probably should be a combo of
errors
andwarnings
?Also: see #416, probably want the following parser options, too:
@jfmengels this is probably another way to steer users towards static analysis. I have felt like the
errors
andwarnings
shared configs were not named clearly, anyway. Probably will keep them since it doesn't hurt, but merge them (or maybe just takeerrors
) for therecommended
version.The text was updated successfully, but these errors were encountered: