-
Notifications
You must be signed in to change notification settings - Fork 170
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
write and verify rules.json
#4590
Conversation
I'm happy with this! However it may not be what you want, since it will break if one of the Another option is adding a specific version of the |
Great points! My gut is that in practice we won't get bitten here too often. My thinking being:
I guess I'm inclined to take the "simple" approach first and rethink if it becomes a problem down the road. How does that sound? |
Sounds good to me :) Thanks for working on this! |
Regarding this, won't the version of |
It's kind of in an awkward spot for now. Since the analyzer still points to the the linter rule documentation rather than the diagnostic version for lints, I try to keep it up to date for Once we switch to pointing to consistent diagnostic information, I don't think this will be a problem anymore. |
* write and verify `rules.json` * ++
Fixes #4587
@parlough: let me know if this is what you had in mind?
/cc @bwilkerson @srawlins