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
Fix: no-new-wrappers reports only wrappers #11984
Conversation
From the history it seems that I'd be happy to prepare PR to check |
they're not wrappers, but since those things are always objects and never functions, it's never code that should ship to production. Perhaps the replacement could merge before this fix? |
Would be good to merge both at the same time, or maybe better have a single PR for both changes. (of course, all this if it's acceptable for a semver-minor to have more warnings in |
I think we need an RFC with more specific details to show the full design needed to solve this issue. |
How do we want to proceed here? |
I'd recommend we merge this PR and update |
PR #12909 |
@mysticatea can you take a look at the merge conflicts on this? |
The commits in this PR have been included in #12909, so closing this one. |
What is the purpose of this pull request? (put an "X" next to item)
[X] Bug fix
Tell us about your environment
What parser (default, Babel-ESLint, etc.) are you using?
Default.
Please show your full configuration:
What did you do? Please include the actual source code causing the issue.
What did you expect to happen?
No errors because those are not wrappers.
What actually happened? Please include the actual, raw output from ESLint.
What changes did you make? (Give an overview)
This PR makes
no-new-wrappers
reporting only wrappers.I guess that
no-obj-calls
rule is a more proper place to report it.Is there anything you'd like reviewers to focus on?
Is this direction correct?