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
I think it would be better if we rename the "isHidden" field to "isVisible". When a user wants to build a form, the form should show specific fields if a radio button or a checkbox is clicked and not hide them.
For example: 'nutzungsart-wohnen' in 'nutzungsart'|answer
is more understandable than !('nutzungsart-wohnen' in 'nutzungsart'|answer)
The text was updated successfully, but these errors were encountered:
Actually, this behaviour is absolutely by design. If we'd name it isVisible we'd have to put in a value true per default. The default state of a field should always be "visible"..
The default state would then be hidden, right? So if we change any related value it'd have to parse the expression again which would turn the value into some indeterminate state (running promise). So if we have an indeterminate state on a property isVisible we'd have to assume that it is false, right. This would cause a flickering form because every value change triggers recalculations of related isVisible fields
I think it would be better if we rename the "isHidden" field to "isVisible". When a user wants to build a form, the form should show specific fields if a radio button or a checkbox is clicked and not hide them.
For example:
'nutzungsart-wohnen' in 'nutzungsart'|answer
is more understandable than
!('nutzungsart-wohnen' in 'nutzungsart'|answer)
The text was updated successfully, but these errors were encountered: