I have a form that does dependencies off a property utilizing oneOf, whenever selections are made down one branching path (3 nested dependencies deep) and then the top level gets changed the form retains the properties and values that were selected previously as well as their new selections. This is interfering with one of our steps where it is conditional using if depending on if a certain path was taken... is there anyway to change this behavior? I saw some references when researching online to a callback functionality that wipes dependent properties whenever the top level changes but not sure if that is compatible with the current scaffolder. Does anyone know of a way around this?
#Scaffolder form retains dependent selection properties and values whenever top level changes
4 messages · Page 1 of 1 (latest)
From digging in it seems like maybe an OmitExtraData and LiveOmit option was recently added though the github threads also maybe make it seem like it doesn't work right, does anyone know how to go about adding those into our template?
I have the same issue. Usually, one way I overcome this is to just always use the top level in the condition. So if (A === true) opens up B, in the steps where I use B I would always check if (A === true) first
The issue is I have a triple nested dependency and one of the steps is trying to check for that second layer selection to know if it should go or not :/ trying to think of ways around it