Conditional property is not added to the form if its type conflicts with `additionalProperties`

[nickgros]

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 or a shared playground link demonstrating the issue.

What theme are you using?

core

Version

5.0.0-beta.10

Current Behavior

My schema should add a "string" field but it only does so when additionalProperties is

• undefined
• true (this is not a real workaround because of Clicking add button when additionalProperties: true doesn't create a new property #3179)
• `{ "type": "string" }

This warning is logged to the console when the field should be added:

could not merge subschemas in allOf:
Error: Could not resolve values for path:"properties.state.type". They are probably incompatible. Values: 
"string"
"number"

Expected Behavior

The conditional field should appear - I should be able to customize additionalProperties and have conditional fields that do not match the additionalProperties schema.

Steps To Reproduce

Link to reproduction in current playground

Environment

Playground 5.0.0-beta.10

Anything else?

No response

[nickgros]

Looks like the change happened in ObjectField in the TypeScript conversion:
f7a2aff

[stale]

This issue has been automatically marked as possibly close because it has not had recent activity. It will be closed if no further activity occurs. Please leave a comment if this is still an issue for you. Thank you.

[nickgros]

This still reproduces in 5.17.0

[stale]

This issue has been automatically marked as possibly close because it has not had recent activity. It will be closed if no further activity occurs. Please leave a comment if this is still an issue for you. Thank you.

[heath-freenome]

@nickgros can you try the other allOf merge package and see if that fixes this? Also there is the custom allOf merge feature which could help