Update ComplexityVisitor.js to fix RangeError, stack size exceeded error #306
Conversation
This file contains 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
I encountered bug, "RangeError: Maximum call stack size exceeded", that indicates that there's a stack overflow due to excessive recursion. This typically happens when there's an infinite loop or circular reference in the code. This modification ensures that each fragment (in function flattenFragmentSpreads()) is only visited once, preventing infinite recursion. Make sure to test your queries with this modification to see if it resolves the issue. If the problem persists, you may need to inspect your GraphQL queries and schema for any circular references or problematic fragments.
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 encountered bug, "RangeError: Maximum call stack size exceeded", that indicates that there's a stack overflow due to excessive recursion. This typically happens when there's an infinite loop or circular reference in the code.
This modification ensures that each fragment (in function flattenFragmentSpreads()) is only visited once, preventing infinite recursion. Make sure to test your queries with this modification to see if it resolves the issue. If the problem persists, you may need to inspect your GraphQL queries and schema for any circular references or problematic fragments.