fix(core): use relative .nxignore
when walking workspace
#20500
Merged
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.
Current Behavior
When walking the workspace, we add
.nxignore
as a custom ignore file, but this was added as an absolute path. The underlying walk library assumed that any ignore files that are absolute should be used in every directory.Expected Behavior
.nxignore
is added as a relative file name, instead of absolute. This allows the walk library to only use nxignore files in the directory where it finds it. In other words, having an.nxignore
in a directory will cause it to affect itself, and child directories.Related Issue(s)
Fixes #20358