If else and RJSF rendering issues containing it.

[Abhishek-kumar09]

Prerequisites

• [X] I have searched the existing issues
• [X] I understand that providing a SSCCE example is tremendously useful to the maintainers.
• [X] I have read the documentation
• [X] Ideally, I'm providing a sample JSFiddle, Codesandbox.io or preferably a shared playground link demonstrating the issue.

What theme are you using?

material-ui

Version

5.x

Current Behavior

Here is the playground link

I have bunch of nested if else statements, that should show different options when swicthed to different properties. In short:

• I have root level applicationType field, that field is decisive of the other fields.
• Issue: all the fields are shown the time RJSF loads, and it doesnt respect if then else condition. example:
• Issue 2: The duplicative fields, some fields are rendered again even fi they are not in the schema. (the other radio button as well, which I forgot to highlight)
• Issue 3: We use custom styled components, but the styles are not applied to the fields that appear in case we select "kubernetes Manifest" as import type.
• Issue 4: Steps to reproduce:
  1. Select "Kubernetes Manifest" as application type
  2. Select "File Upload" from the drop down
  3. upload the file
  4. Submit the form.

Although, the URL is required for the else part, the form still throws validation errors with message must have required property 'url' screenshot:

Expected Behavior

• The fields should be selectevely loaded on first render, e.g. Where the UI is showing the fields just for selected item on first load, and doesn't populate everything.

• There should not be duplicate field during render.

• Correct validation errors on submit

Steps To Reproduce

Described above

Environment

- OS: MacOSX
- Node: 16
- npm: 8.19

Anything else?

No response

[harkiratsm]

Related from https://github.com/rjsf-team/react-jsonschema-form/pull/3763 https://github.com/rjsf-team/react-jsonschema-form/pull/3767

^^ @heath-freenome @nickgros

[heath-freenome]

This requires implementing a new feature similar to ui:fieldReplacesAnyOrOneOf except that it would be ui:anyOrOneOfReplacesField. In the SchemaField we render both the field and the anyOf/oneOf. With this flag turned on then I would imagine that the field is not rendered since the anyOfOneOf will do it. This would required some verification of it working properly, including some decent unit tests. We could use some help for this.