-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Infinite $ref recursive error via computeDefaults #1160
Closed
3 tasks done
dok opened this issue
Jan 30, 2019
· 4 comments
· May be fixed by domharrington/react-jsonschema-form#1
Closed
3 tasks done
Infinite $ref recursive error via computeDefaults #1160
dok opened this issue
Jan 30, 2019
· 4 comments
· May be fixed by domharrington/react-jsonschema-form#1
Labels
Comments
Gigantic blocker for me. |
miscounting
pushed a commit
to miscounting/RewardBotJ
that referenced
this issue
Jul 12, 2020
Due to rjsf-team/react-jsonschema-form#1160 there's some problem with recursive schemas. Created a subtype of Action called AfterAction which (according to the schema) cannot have a timeout field, which allows the form to render.
7 tasks
7 tasks
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please leave a comment if this is still an issue for you. Thank you. |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prerequisites
Description
I'm able to consistently reproduce a maximum callstack error. Here is an image of the error.
I believe this is due to the
utils.computeDefaults
method, that recursively follows a $ref.Steps to Reproduce
Copy and paste these snippets into their respective input fields in the playground.
JSONSchema
UISchema
FormData
Expected behavior
I'm not sure what the expected behavior for this type of behavior is. Since the
$ref
object does not have a.default
property, should it exit out of the recursive loop?Actual behavior
Version
1.2.0
The text was updated successfully, but these errors were encountered: