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
Fix: don't throw if rule is in old format (fixes #6848) #6850
Conversation
@vitorbal, thanks for your PR! By analyzing the annotation information on this pull request, we identified @mysticatea to be a potential reviewer |
LGTM |
LGTM, waiting for others to review. |
Question: Do we want to tolerate Example: // Header comments
// Requirements, etc.
exports.meta = {
docs: {},
fix: false,
recommended: false,
schema: []
};
exports.create = function(context) {
// etc.
}; |
@gyandeeps It does impact our build tooling though, so one could argue |
LGTM, thank you! As the history of the file, |
@platinumazure IMO I think it would be valuable to lint against the exports assignment style you mentioned. So I'm 👍 for linting for the correct exports format :) |
This is an internal rule that should only be used on ESLint repository, while style shown by @platinumazure is valid, it's not the style we use for our rule, and will be noted during code review. So I think this rule doesn't need to check that style. If anything, we might want to create another rule that would enforce |
What issue does this pull request address?
#6848:
internal-no-invalid-meta
was throwing an error when it ran on a rule in the old format.What changes did you make? (Give an overview)
I changed
internal-no-invalid-meta
so it now reports a linting error when the rule is in the old format, instead of throwing an unrecognizable error.Is there anything you'd like reviewers to focus on?
Nothing in particular.