diff options
author | caalador <mikael.grankvist@gmail.com> | 2017-02-09 09:32:57 +0200 |
---|---|---|
committer | Denis <denis@vaadin.com> | 2017-02-09 09:32:57 +0200 |
commit | 43600310195bdce4caa5c24e03227b9925e1934c (patch) | |
tree | 5a319e6b2f8765c0e00282de053de778be913339 /tests | |
parent | b772f4c8f015fdd91a64e16a7c48a74b18108c76 (diff) | |
download | vaadin-framework-43600310195bdce4caa5c24e03227b9925e1934c.tar.gz vaadin-framework-43600310195bdce4caa5c24e03227b9925e1934c.zip |
Binding a null bean should clear the bound field values (#8288)
* Add clear field values #8287
Added functionality to make it possible to clear bound field values manually
or when setting a null bean to binder.
Binder will now clear bound fields for setBean(null) or if using readBean() functionality
when calling the clear() method. Binder.clear() will throw a IllegalStateException if
we have a bound bean.
* MultiSelectionModel MultiSelect should implement emptyValue
* Removing public clear() method and clearing field values only through
setBean(null) and readBean(null) to be consistent and not have
confusing functionality.
* Simplified clearFields() as we don't need to check if field is readOnly
* Document in removeBean JavaDoc that it will also clear the bound fields
if we have a bean the is removed.
* Binder should not have changes after clearing fields.
* Add getEmptyValue as default to MultiSelect.
Multiselect default for empty value should be an empty set.
* Revert "Add getEmptyValue as default to MultiSelect."
This reverts commit 45de8f45c4a1e3e45ab8a0353ab2a48bb4f1be6f.
* Merge branch 'master' into issue/8287_Clear_bound_fields
* Remove override for default implementation.
* Fire status change event on clearFields if we had changes before clearing.
* Formatting.
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions