Properties whose available options change via dependency creates an unresolvable state for users

[joesolly]

Prerequisites

• I have searched the existing issues
• I understand that providing a SSCCE example is tremendously useful to the maintainers.
• I have read the documentation
• Ideally, I'm providing a sample JSFiddle, Codesandbox.io or preferably a shared playground link demonstrating the issue.

What theme are you using?

core

Version

5.24.1

Current Behavior

When I create a property dependency and the dependent property is an array with multiple options whose options change based on the dependency, if I start to select options, then switch the dependent field, the formdata does not clear the invalid options.

Expected Behavior

Invalid array options are cleared when the available list of options changes

Steps To Reproduce

Playground Sandbox Link

1. Create a property with a selectable option, say product type {'fruit', 'dairy'}
2. Create a dependent property that is an array whose options change, 'fruit' -> 'apple', 'banana' and 'dairy' -> 'milk', 'cheese'
3. Selecting 'apple' then switching to 'dairy' leaves a user in an uncorrectable state because 'apple' stays in the form data

See the video of me demonstrating it with the Playground Sandbox

Screen.Recording.2025-01-23.at.9.47.20.AM.mov

Environment

- OS:
- Node:
- npm:

Anything else?

No response

[joesolly]

This might be related to #3894

[heath-freenome]

@joesolly It definitely seems related. Are you interesting in figuring out how to fix it by adding a new feature?

[joesolly]

@joesolly It definitely seems related. Are you interesting in figuring out how to fix it by adding a new feature?

@heath-freenome I'd be willing to take a stab at it if you have an idea of where to point me. I'm currently working around this by hardcoding clearing the formdata when the particular field changes.

[heath-freenome]

@joesolly The culprit is likely the sanitizeDataForNewSchema() function in the @rjsf/utils package. It currently does not have logic for dealing with anyOf/oneOf in either an object or and array>items situation. It's also possible that it needs to deal with dependencies as well (although it does use retrieveSchema which theoretically handles dependencies for us). We'd love help expanding it's capabilities.

Thanks!