Overly deep nesting of objects, there is an error in assigning values to formData.

[amazingywk]

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

Current Behavior

In this playground example，When we change the value of dropdown A, B and C do not appear in formData. We suspect that it is a bug caused by overly deep nesting of objects.

{
  "type": "object",
  "properties": {
    "abc": {
      "type": "object",
      "properties": {
        "a": {
          "type": "string",
          "enum": [
            "aaa",
            "bbb"
          ],
          "enumNames": [
            "test1",
            "test2"
          ],
          "default": "aaa"
        }
      },
      "dependencies": {
        "a": {
          "oneOf": [
            {
              "properties": {
                "a": {
                  "enum": [
                    "bbb"
                  ]
                },
                "b": {
                  "type": "object",
                  "properties": {
                    "c": {
                      "type": "string",
                      "enum": [
                        "withBefore"
                      ],
                      "enumNames": [
                        "111"
                      ],
                      "default": "withBefore"
                    }
                  }
                }
              }
            },
            {
              "properties": {
                "a": {
                  "enum": [
                    "aaa"
                  ]
                }
              }
            }
          ]
        }
      }
    }
  }
}

Expected Behavior

No response

Steps To Reproduce

No response

Environment

- OS:
- Node:
- npm:

Anything else?

No response

[heath-freenome]

@amazingywk I added a shared link to your description above with your example. When I try it out it seems to be working fine. Can you provide a screen recording of what you believe isn't working?

[amazingywk]

@amazingywk I added a shared link to your description above with your example. When I try it out it seems to be working fine. Can you provide a screen recording of what you believe isn't working?

when you choose "a" into "test2", the right place show "b" and "c", but in the formData, "b" and "c" did not appear and were not assigned values. This can also lead to other problems: if I set another variable "d" that depends on "b" and "c", then this "d" may not even appear on the right side.

[heath-freenome]

@amazingywk The fact that 111 is should up is the result of the UI rendering and the enum only having a single value with a default. Any yet when I tried a playground with the dependencies removed I do see the default value showing up. So it looks like you have found a bug in how we process dependencies while defaulting.

[heath-freenome]

@abdalla-rko I am not sure whether your fix for #4282 covered this case. Do you have time to investigate?

[amazingywk]

@abdalla-rko I am not sure whether your fix for #4282 covered this case. Do you have time to investigate?

The version in my project is 1.8.1 and there is no such problem. But this is not the key to the problem. Because I reproduced this problem on the playground. There is no problem locally. However, local debugging is not as efficient as the playground. Perhaps you haven't updated the playground version? If it is the latest version, then I understand that there should be this problem in your latest version.

[abdalla-rko]

Hi @amazingywk, not sure what you mean by version 1.8.1 and for what it is. But I could reproduce the issue easily on the playground and just did a pr for the fix. It should be fixed once it's merged.

[amazingywk]

你好@amazingywk，不确定你说的 1.8.1 版本是什么意思，也不知道它是什么。但我可以在操场上轻松重现这个问题，只需为修复做一个 pr 即可。合并后应该会修复。

thank you!