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
Currently, pyxform does not require labels for items in choice lists.
For dynamic selects, I can see an argument for them not being required because users could be building a list they only want to query and won't use in a select. However, I think that's pretty rare and for those advanced users, it's not a big deal to just add a label. In v1.4, if a user did build a dynamic select with a choice missing a label and used it in a select, there'd be a Validate error. In v1.5, there's a crash (narrowly addressed by #535).
For static selects, I don't see any use for a choice without a label. Currently there's no validation on this at all.
There's probably no particular harm in requiring the form designer to always add a text label to everything - even if the appearance may hide them. But making them mandatory may result in the inability to prevent any text being displayed should they desire a purely pictorial interface for the selection (for whatever reason...); eg I dont think you can otherwise hide the label being shown for a map.
Maybe this could be thought of as "if the XForm result for this choice is going to be empty itext then raise an error" e.g. either a label, or a translation, or some kind of media.
Currently, pyxform does not require labels for items in choice lists.
For dynamic selects, I can see an argument for them not being required because users could be building a list they only want to query and won't use in a select. However, I think that's pretty rare and for those advanced users, it's not a big deal to just add a label. In v1.4, if a user did build a dynamic select with a choice missing a label and used it in a select, there'd be a Validate error. In v1.5, there's a crash (narrowly addressed by #535).
For static selects, I don't see any use for a choice without a label. Currently there's no validation on this at all.
CC @MartijnR @pbowen-oc
The text was updated successfully, but these errors were encountered: