-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RangeError: maximum stack size exceeded error (refers to #18) #19
Comments
Hello ! We still have this problem. Has anyone found a solution? |
🎉 This issue has been resolved in version 2.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Due to the recent changes, when the schema is being defined as a ref to itself (recursive) with an overridden
description
property, it causes the StackOverflow error in json-schema-tree.Example:
Context
This causes the
Error: Stack size exceeded
rendering on HttpOperation node where such schema is referencedCurrent Behavior
Expected Behavior
The schema is rendered correctly and doesn't make the page to load till the stack size is exceeded (provoking the browser page unresponsiveness)
Possible Workaround/Solution
#18 caused this
newFragment = { ...newFragment };
- this is the line inwalker.js
file causing the referential inequality that later as far as I grasped leads to the infinite ref resolvingSteps to Reproduce
Environment
Chrome: 39
,node.js: 5.4
): Chrome latestThe text was updated successfully, but these errors were encountered: