Encourage warning messages for onFulfilled
or onRejected
being promises
#134
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.
This is probably the most common error I see from beginners using promises on stack overflow (e.g. http://stackoverflow.com/questions/17517593/more-complex-deferred-promise-usage-and-chains-just-arent-clicking-would-love/17525172). They call the function, rather than passing the function to
.then
. Since I can't see why anyone would intentionally pass a promise to a.then
handler and these sorts of functions almost always return promises, I think this could be a big win for helping people get started faster.P.S. the PR is just there as a discussion point, I'm happy to re-word/move it as appropriate.