-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
doc: clarify stdout/stderr arguments to callback #6015
Conversation
@nodejs/documentation |
LGTM, but the commit log says |
heh, sigh... it's late |
a0e0a88
to
746a543
Compare
Fixed |
LGTM |
The `stdout` and `stderr` arguments passed to the callback will contain the | ||
stdout and stderr output of the child process. By default, Node.js will decode | ||
the output as UTF-8 and pass strings to the callback. The `encoding` option | ||
(see below) can be used to specify the character encoding used to decode the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would either link to encoding
or just leave off the (see below)
. These things tend to become wrong when things get moved around.
Clarify that the arguments to child_process.execFile and child_process.exec callback can be Buffer or strings. Fixes: nodejs#3389
746a543
to
8c8910e
Compare
@cjihrig ... pulled out the |
LGTM |
Landed in 6fd26dc |
Pull Request check-list
existing APIs, or introduces new ones)?
Affected core subsystem(s)
doc
Description of change
Clarify that the arguments to fs.execFile and fs.exec callback can be Buffer or strings.
Fixes: #3389