Cannot modify an anyOf object field when the defaults are set in the schema

[binhtran04]

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.8

Current Behavior

I have an object field in my form that takes two options 1 and 2. Option 1 has attributes a, b, c. Option 2 has x, y, z.
The schema defines the field defaults as {x: 0.045, y, 0.0015, z: 0}
The result is that I cannot modify the field when option 2 is selected. For instance, when typing in the x input, it stays at 0.045

Here is the playground link

Expected Behavior

I can edit the x, y, or z inputs

Steps To Reproduce

1. open the playground link
2. select the option 2
3. type some number in the x input

Environment

- OS:Ubuntu
- Node:22
- npm:

Anything else?

I think this is a bug with 5.24.x version.
When I revert to 5.23.2, the field is editable again
No response

[heath-freenome]

@abdalla-rko I wonder if one of your changes in 5.24.x caused this? Do you have time to investigate?

[Geylnu]

@heath-freenome Still have the issue in 5.24.9, did this release work?

[heath-freenome]

@Geylnu Dang, I was hoping the fix that @abdalla-rko put in would solve it. Looks like it wasn't tested in the playground with your example. Sorry. I hope that we can get you a fix soon.

[abdalla-rko]

Sorry, I should have tested your schema as a final check. I just simplified the schema and removed the definitions and so the first pr was only for the combinators issue. Your issue is a combination of combinators and definitions. I have now solved the issue for referenced schemas(definitions) and it should work in the next release.

[enzoferey]

Hello team, this one seems to have introduced a regression on our end.

We no longer can change values in oneOf with a default value.

I unfortunately cannot provide a reproduction on the playground (which version is being used there though? The faulty one we have identified is 5.24.9), but here is our setup =>

(changing objectType does not work)

JSON schema:

{
  "type": "object",
  "properties": {
    "objectType": {
      "title": "Object type",
      "type": "string",
      "oneOf": [
        {
          "const": "company",
          "title": "Company"
        },
        {
          "const": "person",
          "title": "Person"
        }
      ],
      "default": "company"
    }
  },
  "allOf": [
    {
      "if": {
        "properties": {
          "objectType": {
            "const": "company"
          }
        }
      },
      "then": {
        "properties": {
          "companyId": {
            "type": "string"
          }
        },
        "required": [
          "companyId"
        ]
      }
    },
    {
      "if": {
        "properties": {
          "objectType": {
            "const": "person"
          }
        }
      },
      "then": {
        "properties": {
          "personId": {
            "type": "string"
          }
        },
        "required": [
          "personId"
        ]
      }
    }
  ],
  "required": [
    "objectType"
  ]
}

Defaults prop config:

experimental_defaultFormStateBehavior={{
  emptyObjectFields: "skipEmptyDefaults",
  arrayMinItems: {
    populate: "never",
  },
  constAsDefaults: "skipOneOf",
}}

[heath-freenome]

@abdalla-rko Can you see if your fixes take care of this new use case?