Detect circular references and return early#69
Open
iamvery wants to merge 4 commits intodchester:masterfrom
Open
Detect circular references and return early#69iamvery wants to merge 4 commits intodchester:masterfrom
iamvery wants to merge 4 commits intodchester:masterfrom
Conversation
This corrects an issue where non-circular references were falsely detected as _all_ seen objects were stored across the entire recursion.
Author
|
It looks like the version of Node used in CI doesn't support |
|
It looks like this handles references in objects. What happens if the circular reference occurs within an array? var containsItself = ['value'];
containsItself.push(containsItself);
var results = jp.query(obj, '$..*'); |
Author
|
Nice catch! Unfortunately there seems to be some other more subtle issue as well. I have yet to reproduce it in this lib's test suite, but in my application code the terminal completely hangs when traversing the problematic object. Interestingly, when I remove the "fix" I added to account for non-circular repetition then things run fine... Where's the loop??? 🤔 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
descendavoids visiting it again.Hope you find this useful! Let me know if somethings needs more work ❤️