anyOf with type boolean doesn't work

[abdalla-rko]

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

6.1.2

Current Behavior

Schema with an anyOf array with a nested object with type boolean doesn’t work properly. Selecting the boolean option in the anyOf field sets the anyOfField value to 1 instead of true in formData.

Expected Behavior

Selecting the boolean option in the anyOf Field should work and the anyOfField value should be a boolean (true/false).

Steps To Reproduce

1. Click here to open the playground demo.
2. Select the boolean option in the anyOf Field.
3. Notice that you can’t select it and anyOfField formData becomes 1 instead of true.

Environment

- OS:
- Node:
- npm:

Anything else?

No response

[echarbeto]

Hey @abdalla-rko,
I think what you’re seeing comes from the fact that the parent schema is self-contradictory: you need to include every type you want to allow at the same level as anyOf.

In the original example, anyOfField is declared with a single top-level type ("type": "number"), while anyOf contains string and boolean branches. Since sibling keywords are combined, that effectively prevents non-number branches from behaving correctly in the UI.

A schema that works is:
"anyOfField": { "title": "anyOf Field", "type": ["string", "boolean", "number"], "anyOf": [ { "type": "string", "title": "string", "enum": ["string"] }, { "type": "boolean", "title": "boolean", "const": true }, { "type": "number", "title": "decimal", "enum": [1.5] }, { "type": "number", "title": "number", "enum": [-3] } ] }

One odd thing: it looks like the order of the union types in type: [] can affect UI coercion (even though order shouldn’t matter for validation). For example:

type: ["string", "number", "boolean"] → selecting the boolean option gets coerced to a number (true becomes 1)

type: ["string", "boolean", "number"] → selecting the boolean option stays a boolean (true)

Not sure if treating type ordering as a “preferred cast” is intended, but that’s what I’m observing.

[heath-freenome]

@abdalla-rko Following up on @echarbeto comment, I tried it out in this playground as was suggested and it works.