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
Error messages are not being propagated correctly for json object schemas.
For instance I have these two schemas, when I raise a custom error with schema2 it works nice as expected & described on the documentation. But when I do the same, but for schema which has a type object it doesn't work.
Fixesrjsf-team#4382
- Updated `NumberField`'s `handleChange` callback to pass through the `errorSchema` and `id`
- Updated the peerDependencies for the packages to be `5.23.x`
- Updated `CHANGELOG.md` accordingly
…nge (#4395)
Fixes#4382
- Updated `NumberField`'s `handleChange` callback to pass through the `errorSchema` and `id`
- Updated the peerDependencies for the packages to be `5.23.x`
- Updated `CHANGELOG.md` accordingly
Prerequisites
What theme are you using?
core
Version
5.x
Current Behavior
Error messages are not being propagated correctly for json object schemas.
For instance I have these two schemas, when I raise a custom error with
schema2
it works nice as expected & described on the documentation. But when I do the same, but forschema
which has a typeobject
it doesn't work.I have created the following playground that allows you to play & to check the current behavior ⬇️
https://codesandbox.io/p/sandbox/rjsf-custom-error-ql66mh?workspaceId=7d9d1079-911b-4954-9a3d-7c3de5279f0c
Expected Behavior
Custom errors should show regardless of the schema used, which means it should show on both described scenarios.
Steps To Reproduce
object
, no error is shown.Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: