Detect circular references and return early #69
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.
I ran into this issue today while dealing with a large object tree that contained circular references. Due to the recursive nature of the path I was using, the result was a
RangeError: Maximum call stack size exceeded
. For my particular use case, it would be preferable for jsonpath to be resilient to such cases by avoiding traversing circular references again.My solution is keep a set of visited objects as the tree is traversed. If the same object shows up twice then
descend
avoids visiting it again.Hope you find this useful! Let me know if somethings needs more work ❤️