docs(eslint-plugin): [no-base-to-string] correct documented default for ignoredTypeNames#12469
Conversation
|
Thanks for the PR, @zaewc! 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 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
View your CI Pipeline Execution ↗ for commit 76b4eec
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #12469 +/- ##
==========================================
+ Coverage 87.06% 94.74% +7.68%
==========================================
Files 514 223 -291
Lines 16616 11426 -5190
Branches 5193 3809 -1384
==========================================
- Hits 14467 10826 -3641
+ Misses 1461 255 -1206
+ Partials 688 345 -343
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
…ect default options
PR Checklist
Overview
The
ignoredTypeNamessection stated that{ ignoredTypeNames: ["RegExp"] }was the default options, but the rule's actual default is["Error", "RegExp", "URL", "URLSearchParams"]Rather than duplicating the full default list in the prose, this removes the misleading "default" wording entirely, per the maintainer's suggestion in the issue - the correct default is already documented just above via the auto-inserted option description (
Default: ["Error","RegExp","URL","URLSearchParams"])