-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
chore: remove Rule
& FormatterFunction
from shared/types.js
#19556
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
Conversation
✅ Deploy Preview for docs-eslint canceled.
|
It looks like this information is duplicated from where types are being pulled now: Maybe we should dedupe and use the imported types from |
20a7f1b
to
79a33f6
Compare
Yes, updated. |
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.
The type for individual rules is actually Rule.RuleModule
from index.d.ts
. That contains the JavaScript-specific definition of a rule. RuleDefinition
is a generic rule without JS-specific information.
@nzakasThanks! Updated 👍🏻 |
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.
As a finishing touch, can we remove the Rule
type from shares/types.js
?
Makes sense, I removed |
Rule
& FormatterFunction
from shared/types.js
Rule
& FormatterFunction
from shared/types.js
Rule
& FormatterFunction
from shared/types.js
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. Thanks!
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[x] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:
What changes did you make? (Give an overview)
Updated
RuleMeta
types to supportdialects
&language
propertiesIs there anything you'd like reviewers to focus on?