-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore(eslint-plugin): switch auto-generated test cases to hand-written in no-base-to-string.test.ts #11273
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
base: main
Are you sure you want to change the base?
Conversation
Thanks for the PR, @nayounsang! 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 d21ff60.
☁️ Nx Cloud last updated this comment at |
"false + '';", | ||
"false + 'text';", | ||
'false + true;', | ||
'false + false;', |
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.
'false + true;',
'false + false;',
'true + true;',
'true + false;',
In my opinion, it would be neater to leave only one of these.
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.
Okay, I guess I can remove duplicate or unnecessary test cases now that I've changed to hand-written ones, but there are more than I thought and it's confusing me.
Let's go through this step by step with me. Excuse me, but I need to ask for your help!
"`${__dirname === 'foobar'}`;", | ||
'`${{}.constructor()}`;', | ||
'`${() => {}}`;', | ||
'`${function () {}}`;', | ||
|
||
// operator + += |
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.
Many of the test cases in the operator +
section are essentially duplicates that only differ in operand order. We could consider reducing them by half.
related to this comment: #11273 (comment)
PR Checklist
Overview