You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently upgraded to 2.8.4 and noticed that our form schemas' conditionals are no longer working. 2.8.1 seems alright whereas 2.8.2 isn't, so I believe this is the PR that broke it.
Expected Behaviour:
When selecting multiple options from the Select widget, each option selected should cause corresponding numerical fields to appear.
Current Behaviour:
The numerical field for only the first option selected appears.
I noticed that in 2.8.1's __evaluateVisibilityIf function, the value param would come in as "Option #1", "Option #2", etc.
in 2.8.4, only "Option #1" is ever passed into the function.
The text was updated successfully, but these errors were encountered:
aharaguchi
changed the title
visibilityIf no longer works with multiple Select widgets
visibilityIf no longer works when target is multiple Select widget
Nov 2, 2022
Ooo thank you so much @KBroichhausen , this is awesome! I saw your PR but wasn't able to find the time to look into exactly what was going wrong with the issue. Appreciate it.
We recently upgraded to
2.8.4
and noticed that our form schemas' conditionals are no longer working.2.8.1
seems alright whereas2.8.2
isn't, so I believe this is the PR that broke it.Expected Behaviour:
When selecting multiple options from the Select widget, each option selected should cause corresponding numerical fields to appear.
Current Behaviour:
The numerical field for only the first option selected appears.
I noticed that in
2.8.1
's__evaluateVisibilityIf
function, thevalue
param would come in as "Option #1", "Option #2", etc.in 2.8.4, only "Option #1" is ever passed into the function.
Form Schema:
The text was updated successfully, but these errors were encountered: