Skip to content

doc: update promisify() docs with behavior when bad arguments are passed #17593

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.

Sign up for GitHub

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

Closed
lossycache wants to merge 3 commits into from
Closed

doc: update promisify() docs with behavior when bad arguments are passed #17593

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2067648
doc: update promisify docs with behavior when bad arguments are passed
lossycache Dec 10, 2017
1c272f9
doc: use 'Node.js style' callback
lossycache Dec 10, 2017
e215574
doc: fix line length and wording
lossycache Dec 12, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
doc: use 'Node.js style' callback
  • Loading branch information
@lossycache
lossycache committed Dec 12, 2017
commit 1c272f9ca679e739c5e2a82cdd27a86ce6ae690d
4 changes: 2 additions & 2 deletions doc/api/util.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -554,8 +554,8 @@ will return its value, see [Custom promisified functions][].
`promisify()` assumes that `original` is a function taking a callback as its
final argument in all cases. If `original` is not a function, `promisify()`
will throw an error. If `original` is a function but its last argument is not a
node-style callback, it will be still be passed a node-style callback as its last
argument anyways.
Node.js style callback, it will be still be passed a Node.js style callback as its last
argument.

### Custom promisified functions

Expand Down