Ignore symlinks and hidden (dot) files during --recursive
.
#644
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.
Note that hidden files will always be honored if they are specified explicitly among the paths on the command line. Symlinks encountered during recursive traversal or passed on the command line will only be followed if the flag
--follow-symlinks
is passed. This is meant to avoid symlinks being hidden by shell expansions; for example, runningswift-format *
where the current directory contains a symlink and following that symlink might be surprising to users.This PR also adds a new test target for code in the
swift-format
binary in order to testFileIterator
without factoring the binary's code out to a separate library target. We should use this in the future to expand coverage of other functionality like the frontends and commands.Fixes #643.