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
A timestamp with the alt-datetime widget is placed in two layers of objects. It is required at the lower layer, but it is possible to submit the form without filling it in:
Expected Behavior
There are a couple similar / simpler cases that work correctly:
@samath117 It's expected that if object_with_timestamp is not required, then you can submit it without filling out the field. The validation with the regular datetime widget is HTML5/browser validation, which is not controlled by RJSF other than globally enabling/disabling it, which is why you see different behavior.
Ah, apologies, I was missing another variant: With the default text widget, the behavior is the same as the datetime widget: Object with String Variant
That is, there is no need to also require the intermediate layer in the normal text widget. The select and radio widgets (when the string has an enum) also have the same behavior. So the bug either lies with all other widgets or with the alt-datetime widget alone.
Prerequisites
What theme are you using?
core
Version
5.x
Current Behavior
Consider the form at this shared playground link.
A timestamp with the alt-datetime widget is placed in two layers of objects. It is required at the lower layer, but it is possible to submit the form without filling it in:
Expected Behavior
There are a couple similar / simpler cases that work correctly:
Steps To Reproduce
No response
Environment
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: