-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
docs(website): mention how rule options should be handled #7713
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
docs(website): mention how rule options should be handled #7713
Conversation
Thanks for the PR, @Josh-Cena! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
❌ Deploy Preview for typescript-eslint failed.
|
docs/developers/Custom_Rules.mdx
Outdated
type Options = [ | ||
{ | ||
preferredCase?: 'lower' | 'upper'; | ||
}, | ||
]; |
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.
I have one question: should this be the type before or after validation (and applying defaults)? My guess is "after", but I don't know if it's used elsewhere than checking defaultOptions
and typing the options
parameter.
2e7cf42
to
8626d02
Compare
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.
Nice example! 💯
PR Checklist
Overview