Conditional property is not added to the form if its type conflicts with `additionalProperties` · rjsf-team/react-jsonschema-form#3178

(7 留言) (0 反應) (1 負責人)TypeScript (13,175 star) (2,136 fork)batch import

additionalPropertiesbughelp wantedif-then-else

描述

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 #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

貢獻者指南

技術棧: reacttypescript
領域: frontend
議題類型: bug
難度: 3
預計時間: 1-2 days
活動狀態: blocked
清晰度: clear
前置要求: ReactJSON Schemareact jsonschema form basics
新手友善度: 40
研究方向: Investigate the schema merging logic in the utils/schema/mergeSchemas.ts file, specifically how allOf subschemas interact with additionalProperties. The error log indicates a conflict between property types in conditional then schemas and additionalProperties. Look at the existing PR #3179 for related work and comments from maintainers to understand the intended fix.