fix: query with workspace descendents #6782
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.
Fixes npm/statusboard#703
In scenarios where one workspace has a dependency on another workspace,
querySelectorAll
may omit some child dependencies. This stems from the fact that the algorithm to find dependencies, starts at the leaf and tries to find a path (followingedgesIn
) which leads back to the selected node. When workspaces are involved you can't reliably walk back up the dependency tree in this direction (ArboristNode
s representing a workspace have noedgesIn
).The proposed fix updates the
hasAscendant
function to also follow thelinksIn
collection when trying to find a path to the selected node.