doc: clarify fs.copyFile() symlink behavior #61669
Open
Conversation
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
Contributor
Author
|
Sorry, I accidentally included a README change from my main branch. I will fix this PR to only include fs.md changes. |
Member
|
Please can you squash your commits, so that |
junnyontop-pixel
force-pushed
the
doc-copyfile-symlink
branch
from
6e9d1a9 to
43c94a9
Compare
junnyontop-pixel
force-pushed
the
doc-copyfile-symlink
branch
from
43c94a9 to
d7f81cb
Compare
Contributor
Author
|
I've squashed the commits into one and fixed the trailing whitespace issue. The commit message has also been updated as you requested. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This PR documents that
fs.copyFile()always dereferences symbolic links, as requested in #61518.When
srcis a symbolic link, the contents of the target file are copied instead of the link itself.Fixes: #61518