You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some cases, an uncaught exception could be thrown from dynamically generated array form fields.
This was happening when a nested array field had an explicitly set 'null' value. This is a
workaround that adds a fallback value to object and array fields to prevent this runtime error. An
issue and fix have also been opened upstream in the react-jsonschema-form repo.
rjsf-team/react-jsonschema-form#2153rjsf-team/react-jsonschema-form#2154
In some cases, an uncaught exception could be thrown from dynamically generated array form fields.
This was happening when a nested array field had an explicitly set 'null' value. This is a
workaround that adds a fallback value to object and array fields to prevent this runtime error. An
issue and fix have also been opened upstream in the react-jsonschema-form repo.
rjsf-team/react-jsonschema-form#2153rjsf-team/react-jsonschema-form#2154
Prerequisites
Description
When formData for an array field is malformed, a runtime error can be thrown.
Steps to Reproduce
formData
field, enter:{ "foo": null }
Expected behavior
Null value should be handled gracefully without throwing an exception
Actual behavior
An uncaught exception is thrown from ArrayField.getDerivedStateFromProps
Version
Tested on 1.7.0 and 2.4.0
The text was updated successfully, but these errors were encountered: