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
Newly created List/Select/MultiSelect widgets (in a View-based form) have empty expressions for theirs values/candidates.
This should mean "no candidate", but because of how ViewFormDescriptionConverterSwitch.getMultiValueProvider(String) is implemented this results in a non-null and non-empty list of candidates/items, with a single "" (empty string) item.
This causes NPEs later when when e.g. trying to determine the id/label/kind of "".
Basically, an empty expression should mean "no candidates" (List.of()), and not as is the case now "a single candidate that is the empty string" (List.of("")).
It's quite annoying because it means these widgets are not "ready to use" (even in an empty but valid state) on creation, and one always has to provide explicit configuration for them.
The text was updated successfully, but these errors were encountered:
Newly created List/Select/MultiSelect widgets (in a View-based form) have empty expressions for theirs values/candidates.
This should mean "no candidate", but because of how
ViewFormDescriptionConverterSwitch.getMultiValueProvider(String)
is implemented this results in a non-null and non-empty list of candidates/items, with a single""
(empty string) item.This causes NPEs later when when e.g. trying to determine the id/label/kind of
""
.Basically, an empty expression should mean "no candidates" (
List.of()
), and not as is the case now "a single candidate that is the empty string" (List.of("")
).It's quite annoying because it means these widgets are not "ready to use" (even in an empty but valid state) on creation, and one always has to provide explicit configuration for them.
The text was updated successfully, but these errors were encountered: