-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore(website): add missing defaultOptions
to custom rule example
#5668
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
Thanks for the PR, @vkarpov15! 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. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
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.
Thanks!
This code snippet is out of date, I'll go ahead and send a followup PR to clean it up...
defaultOptions
defaultOptions
defaultOptions
defaultOptions
to custom rule example
PR Checklist
Overview
Quick suggestion. The sample in the "Type Checking" section almost works, just missing
defaultOptions
. Figured I'd throw this in here.