Overlapping ESLint rules for unnecessary Promise
wrap
#29
Labels
➕ enhancement
new feature or request
Promise
wrap
#29
User story
As an engineer, I want only one ESLint rule to target a given issue, so that I only get one finding per issue and avoid unnecessary noise.
Acceptance criteria
There is only one rule for reporting unnecessary
Promise
wrappers.Minimal reproduction of current behaviour
The promise/no-return-wrap rule included from recommended config here .
The unicorn/no-useless-promise-resolve-reject rule included in recommended config here seems to be an expanded and auto-fixable version of that rule - it includes
finally
andyield
constructs.Desired behaviour showcase
The
promise/no-return-wrap
can be removed.Which configuration is this related to?
default
ESLint version
No response
The text was updated successfully, but these errors were encountered: