Strip irrelevant nodes generated by resolved nodeSelector #52
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.
What this PR does / why we need it:
Documentation structures featuring
nodeSelector
s had some irrelevant, erroneous leftover nodes in the resolved nodes tree.In particular some nodes can could contain
contentSelector
source that referencedtree
GitHub object. This happened when a resolved folder contained no markdown, e.g. images or assets folders containing only multimedia files used in markdowns.In these cases the result was a node with
contentSelector
referencing the folder tree object and no child nodes.This PR introduces a post build cleanup procedure that force removes all references to tree objects and empty folder nodes.
Release note: