Clarify docs for ensureSymlink() when destPath already exists #869
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.
The existing docs for
ensureSymlink()
don't specify what happens in the case wheredestPath
already exists. Looking at the code it turns out that whendestFile
already exists the function exits without making any modifications, whether or notdestPath
is a symlink tosrcPath
:node-fs-extra/lib/ensure/symlink.js
Line 26 in 1625838
I found this behavior surprising, because the function name
ensureSymlink()
sounds like it will ensure that the symlinkdestPath -> srcPath
exists. This PR clarifies the existing behavior in the docs.