no-useless-promise-resolve-reject: Fix typo in lint message
#1736
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Change error message to read `Promise.resolve(value)` instead of `Promise.resolve(error)`
dasa
changed the title
no-useless-promise-resolve-reject: Change MESSAGE_ID_RESOLVE to be more intuitive
sindresorhus
changed the title
no-useless-promise-resolve-reject: Change MESSAGE_ID_RESOLVE to be more intuitiveno-useless-promise-resolve-reject: Fix typo in lint message
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Existing error message:
Prefer `return value` over `return Promise.resolve(error)`This is a little unexpected since it's returning a value rather than an error.
This PR is makes the message read as:
Prefer `return value` over `return Promise.resolve(value)`