As you can see, Schema 1 contains oneOf for Object 2 in visibleIf and is rendered without Object 2 and Schema 2 does not contain oneOf but Object 2 is rendered.
If you flip-flop in Schema 1 to e.g. Value 2 and back to Value 1, you are back at initial state but now Object 2 is visible.
This does not look like it is intended. I would create a PR but currently I do not know why there is different logic for oneOf and without oneOf because I thought this should be equivalent in my case.
It looks like the not visible element in the oneOf part triggers the setVisible method with false.
I have an object
Object 2which only should be visible if:Field 1is equal to valueValue 1orField 2is equal to value1.Now, add some extra:
Field 2is only visible ifField 1is equal toValue 2orValue 3.This simply means that
Object 2is mandatory forValue 1and is optional forValue 2andValue 3, which can be toggled viaField 2.Sounds too complicated...here is a stackblitz: https://stackblitz.com/edit/angular-ivy-ymrftk
As you can see,
Schema 1containsoneOfforObject 2invisibleIfand is rendered withoutObject 2andSchema 2does not containoneOfbutObject 2is rendered. If you flip-flop inSchema 1to e.g.Value 2and back toValue 1, you are back at initial state but nowObject 2is visible.This does not look like it is intended. I would create a PR but currently I do not know why there is different logic for
oneOfand withoutoneOfbecause I thought this should be equivalent in my case. It looks like the not visible element in theoneOfpart triggers thesetVisiblemethod with false.