Grid columns can now be marked as non-editable (#16538)
Non-editable columns are not assigned editor fields. When the editor is active,
any non-editable content is not displayed (this should changein the future).
This is separate from setting the property or editor field read-only - in those
cases the field is still used to display the data which may not be desired and
will fail if there is no converter.
Also add Column.setEditorField(Field<?>) and the corresponding getter.
Change-Id: Ice17c357895cb63a8e1bfd6abaffc1d803399e98
* Removed shortcut interface
* Moved TimeZone converter to a separate class
* Moved Enum converter to a separate class
Change-Id: I2b959e3a002e6319912212df4a62a3bd05677f80
This fixes the issue discussed in #14595 for the framework's internal
tests (if they use MockVaadinSession).
Change-Id: I1956680ac065428be41b2ad43fbb80503351b366
Defer RPC calls in RpcDataProvider to avoid cache issues (#16505)
This patch defers cache refresh and row adding/removing. These calls are
omitted completely when making initial response to the client or
updating the size with bare ItemSetChangeEvents.
Change-Id: I6b350680b3e2381caf6a66c9a4ad283207d024dc
Add methods for getting invalid fields from a FieldGroup (#13775)
* Method for retrieving all failing fields exceptions from a
CommitException
* Methods for handling commit errors in Grid (#16515)
* Show editor row validation errors only on the fields (#16509)
Change-Id: Iabef662579e4ccae3803a513205e46542c41cce2
Conflicts:
server/src/com/vaadin/ui/Grid.java
Declarative for DateFields (and related) with ISO8601 (#16313)
DesignAttributeHandler supports method names that contains some words in
uppercase
DesignAttributeHandler and other components now use extensible Formatter
with Converters rather than static methods
Change-Id: I9f68414bd4821f47ff37a26375091d154cae9a93
Fix RpcDataProvider cache clearing on bare ItemSetChange (#16481)
This patch optimizes value change listeners and updates a bit in order
to make clean up on cache invalidation easier to perform.
Change-Id: I6ae3e0ef5046bd5f404f5e0a440607cabd48c6a4
Don't rely on broken JsonValue.jsEquals semantics (#15508)
This implementation also happens to be slightly faster becasue because
the object and array comparisons does not dump the values into native
representations before comparing. The difference is about 2 ms per
action when setting 40 panels in BasicPerformanceTest. This represents
about 5% improvement in a quite synthetic case.
Change-Id: I6319e268b7155e1123457437d81021296728a386