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
{{ message }}
This repository was archived by the owner on Nov 2, 2023. It is now read-only.
If a form definition has multiple languages and a selectOne has missing human-readable labels in all languages for at least one selectOne option, the form is still valid in Central and Collect, but throws an error in ruODK::form_schema_ext, which assumes that all options have values.
TODO: verify whether this applies to SelectMultiple (assume yes) and single translation. Build and test example forms with missing values.
Error message
"Error in xml_nodeset(NextMethod()): Expecting an external pointer: [type=NULL]"
ODK Build could warn if a form has a blank SelectOne or SelectMultiple option label.
Why so: Is there any reason a form should have no user visible label for an option?
Why not: the XForm and XLSForms specs seem to allow this, seeing that such a form works both in Central and Collect.