-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Open
Labels
any-one-all-ofRelated to fixing anyOf, oneOf or allOfRelated to fixing anyOf, oneOf or allOfbugdefaultshelp wanted
Description
Prerequisites
- I have searched the existing issuesI understand that providing a SSCCE example is tremendously useful to the maintainers.I have read the documentationIdeally, I'm providing a sample JSFiddle, Codesandbox.io or preferably a shared playground link demonstrating the issue.To pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.
What theme are you using?
core
Version
5.x
Current Behavior
When one of the options from anyOf/oneOf is rendered, the default values get set properly. However, after you switch to a different option, then go back, all the defaults will be gone.
Expected Behavior
The defaults should get set every time someone changes the subschema version
Steps To Reproduce
- Go to https://rjsf-team.github.io/react-jsonschema-form/
- Click the "Any Of" example
- Notice that "First method of identification" is selected, and "First name" is set to the default value, "Chuck"
- In the render view, change to "Second method of identification"
- In the render view, change to "First method of identification"
Current: "First name" is empty
Expected: "First name" is set to the default value, "Chuck"
Environment
- OS: Windows 11
- Node & npm: whatever you use on your playground
Anything else?
Metadata
Metadata
Assignees
Labels
any-one-all-ofRelated to fixing anyOf, oneOf or allOfRelated to fixing anyOf, oneOf or allOfbugdefaultshelp wanted
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
mbalc commentedon Jun 19, 2023
nevermind, there's this "Object fields default behavior" thing that you need to change to a different value; maybe consider making it a bit more obvious that this works this way - and consider changing the default value there in the playground away from the legacy option - and you can probably close this issue
nickgros commentedon Jun 23, 2023
@mbalc thanks for the report. The "legacy" behavior is the default in RJSF v5 (it will be changed in in the next major version), so will probably change the default value when v6 is released.
I would actually expect the firstName field to re-populate with the default value under legacy behavior, so I think this is a bug.