Document execCommand noTrim output preservation#485
Merged
steelbrain merged 1 commit intoJun 29, 2026
Conversation
Yurii201811
force-pushed
the
codex/preserve-execcommand-output
branch
from
e9db2db to
ae9e5da
Compare
steelbrain
approved these changes
Jun 29, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
execCommandwithnoTrim: truepreserves leading and trailing blank lines on stdout/stderrnoTrim: truewhen exact command or file output mattersRefs #463
Checks
yarn lint(Node 24.15.0)yarn test --match "has a working noTrim option"(Node 20.20.0 with bundled Python for native test dependencies)