-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix(eslint-plugin): fix no-base-to-string boolean literal check #1850
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, @duduluu! 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. |
Codecov Report
@@ Coverage Diff @@
## master #1850 +/- ##
=======================================
Coverage 94.36% 94.36%
=======================================
Files 166 168 +2
Lines 7608 7651 +43
Branches 2185 2199 +14
=======================================
+ Hits 7179 7220 +41
Misses 183 183
- Partials 246 248 +2
|
@duduluu, thanks for this! With regards to @felixfbecker's comment at #1655 (comment), do you want to support other types here? Selfishly I'm hitting this issue with > /myRegExp/.toString()
'/myRegExp/' |
just |
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.
rc as per request to also support RegExp
Sorry for late, let me try. |
Hi, @bradzacher . Does that mean this PR is unnecessary after the TypeScript merges your fixes for base types' definition? |
No, because there can be people on older TypeScript versions :) |
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.
on change to set the default to be "what it should be".
otherwise, LGTM. thanks
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!
Fixes #1655
Feat: add option ignoreTypeNames