Limit content item recursions to 20 #7500
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 #7451
@jtkech I ended up using both a dictionary and hashset, because comparing by ref wasn't possible, because when it is recursing like this it's creating new shapes everytime, so new objects getting spawned.
I picked 20 as the number, as @jeffolmstead has already experienced the issue you spotted, trying to build multiple display types, on the same content item.
The other option is to remove recursion checking here on this filter completely.
But a bit of bad code, i.e.
{{ Model.ContentItem | shape_build_display | shape_render }}
does stackoverflow the system.