-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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: improve child_process maxBuffer
text
#11791
Conversation
doc/api/child_process.md
Outdated
* [`maxBuffer`][] {number} largest amount of data (in bytes) allowed on | ||
stdout or stderr - if exceeded child process is killed (Default: `200*1024`) | ||
* `maxBuffer` {number} Largest amount of data in bytes allowed on stdout or | ||
stderr. (Default: `200*1024`) If exceede, the child process is terminated. |
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.
typo: exceede
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.
Fixed, thanks!
A key thing this fixes is the confusing alternate formatting for Because it's a link, The link isn't to full information about |
`maxBuffer` information in child_process.md used atypical formatting. This uses a single consistent style for all instances of `maxBuffer` information.
`maxBuffer` information in child_process.md used atypical formatting. This uses a single consistent style for all instances of `maxBuffer` information. PR-URL: nodejs#11791 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Landed in ea5a2f4 |
`maxBuffer` information in child_process.md used atypical formatting. This uses a single consistent style for all instances of `maxBuffer` information. PR-URL: nodejs#11791 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
`maxBuffer` information in child_process.md used atypical formatting. This uses a single consistent style for all instances of `maxBuffer` information. PR-URL: nodejs#11791 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
is this applicable to v6.x? |
@MylesBorins It's a style change, not a content change, so I think the answer is "yes, but it's also not crucial by any stretch". |
maxBuffer
information in child_process.md used atypical formatting.This uses a single consistent style for all instances of
maxBuffer
information.
Checklist
Affected core subsystem(s)
doc child_process