Simplify Binding API by removing the FIELDTYPE type parameter
The type parameter is mainly used internally, the only externally facing
use is to define the exact type of Binding.getField. Code that has
access to a typed instance of Binding does typically also have direct
access to the field instance, so there's no real use for the type
parameter.
Change-Id: Idf2ab18a79ec5f0a7cef83705b8084fbf7014c10
Adds an unresolved validation status to make it possible to clear
visible field validation errors, even if status is not yet valid.
Change-Id: I227a8802b6a71be1533dc903bad1a8e2faef5ed2
BinderStatusHandler is now triggered only once per validation.
Unified ValidationError and BinderResult into BinderValidationStatus.
Renamed ValidationStatusChangeEvent into ValidationStatus.
Unified handler names for validation status.
Next patch will fix resetting of field errors on reset.
Change-Id: I9536d554d781fe599fbd7e5bcb5a9ffebe675ca0
The legacy LoginForm is substituted with the new one which is compatible
in API.
The patch contains modified code from the addon
https://vaadin.com/directory#addon/loginform
Change-Id: I2178291c97c2f66840f832a0bf932271534beb49
Renamed InitializableClientToServerRpc -> InitializableServerRpc and
moved it out from ServerRpc to avoid confusion (#8599)
It is now possible to use RpcProxy.create(class, Connector) before the
connector has been initialized