-
Bug
-
Resolution: Not an issue
-
Major
-
None
-
6.2.12
-
None
Steps to reproduce
- Â Define a select field (tested with ComboBoxfield, listSelectField and radioButtonGroupField with an optionListDatasource using longs for option values.
Example:
comboSelect: label: Select $type: comboBoxField type: java.lang.Double converterClass: com.vaadin.data.converter.StringToDoubleConverter datasource: $type: optionListDatasource options: - name: one label: One value: 1 - name: two label: Two value: 2
- Attempt to make a selection using the dialog
Expected results
The dialog can be saved and the JCR contains Long properties.
The documentation for these fields makes reference to property type and converterClass configuration.
Actual results
On selection, Admin Central shows an error bar and the attached stack trace is logged.
Workaround
None. Dialog can only save string properties.
Acceptance criteria
- is causing
-
MGNLUI-6937 DOC: Note for 'type' field property applies to text fields only
- Closed
- is related to
-
MGNLUI-5471 Allow select fields non-string values (i.e. ditch hardcoded conversion of selected item to link)
- Closed
- is superseded by
-
MGNLUI-6937 DOC: Note for 'type' field property applies to text fields only
- Closed