Nested dynamic schema dependencies

[kalyan542]

I have select box A which has options option1, option2
if select option1 in select box A, populate another select box B with options NORMAL, CMC
If i select Normal in select box B, populate some fields name, age
If select CMC populate fields id, enable

I can able to populate dependency fields based on select box A but not with select box B.

{
type: "object",
properties: {
A: {
"title": A,
"type": "string",
"enum": [
"--select--",
"option1",
"option2",
],
"default": "--select--"
},
},
"dependencies": {
"A": {
"oneOf": [
{
"properties": {
A: {
"enum": [
"option1"
]
},
B: {
type: "string",
title: B,
enum: [
"NORMAL",
"CMC"
],
enumNames: [
"NORMAL",
"CMC"
]
},
name: {
type: "string",
title: "name"
},
age: {
type: "string",
title: "age"
},
}
},
]
}
}
}

[epicfaace]

@kalyan542 Can you please post a playground link (https://mozilla-services.github.io/react-jsonschema-form) demonstrating the issue? That will help us get to the problem faster.

[kalyan542]

Please see this below example.
https://jsfiddle.net/kcherukuri/3asr5Lo2/3/

[kalyan542]

@kalyan542 Can you please post a playground link (https://mozilla-services.github.io/react-jsonschema-form) demonstrating the issue? That will help us get to the problem faster.

Added jsfiddle playground link

[epicfaace]

@kalyan542 What are you expecting? When I select "CMC" I get the following fields, which seems to accord with what the schema describes:

[kalyan542]

Select option1 in select box A show all the fields B,Name,Age,Id,Enable --> this case is working as expected,Struggling with below cases.

only show name and age fields If i select CMC in Select box B
only show id and enable fields If i select NORMAL in Select box B

[epicfaace]

@kalyan542 Does this schema work for you? https://jsfiddle.net/jhocLqvb/

[kalyan542]

B select box has to show after A select box. if i add uiSchema={uiSchema} for fields order getting this error "Invalid root object field configuration:uiSchema order list contains extraneous property 'B'."

[epicfaace]

That error should not come in the latest playground version, since #814 was merged: Playground link. However, this fix has not been released in the latest version yet.

However, there seems to be another problem -- the ui:order is not being respected, probably because of something related to nested dependencies.

[ezzadeen]

This issue seems too old.
I'm using @rjsf/core": "^3.2.1. I don't have this problem.

`
{ "definitions": {
"Root": {
"type": "object",
"properties": {
"first_dependency": {
"type": "string",
"enum": ["yes", "no"]
}
},
"dependencies": {
"first_dependency": {
"oneOf": [
{
"properties": {
"first_dependency": {
"enum": ["yes"]
},
"properties": {
"title": "",
"type": "object",
"properties": {
"nested_dependency": {
"type": "string",
"enum": ["yes", "no"],
"default": "no"
}
},
"dependencies": {
"nested_dependency": {
"oneOf": [
{
"properties": {
"nested_dependency": {
"enum": ["yes"]
},
"properties": {
}
}
},
{
"properties": {
"nested_dependency": {
"enum": ["no"]
},
"properties": {}
}
}
]
}
}
}
}
}
]
}
}
}
}
}

`

[nickgros]

Per @ezzadeen this seems to be fixed. Please open a new issue if any related issues persist.