fix: filter path because a dynamic zone is a component but it should be classified as a dynamic zone #15139
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 does it do?
path.undefined
with dynamic zonesWhy is it needed?
dynamiczone.0
but we don't want the index in these paths so it thinks it should just bedynamiczone.undefined
when looking for components, however this should actually be captured by the dynamic zone findings. It's a bit confusing.Related issue(s)/PR(s)