Skip to content

Vaadin Flow Components V18.0.4
Compare
Choose a tag to compare
@vaadin-bot vaadin-bot released this 11 Jan 09:37
· 27 commits to 18.0 since this release
18.0.4
e472e53
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Vaadin Flow Components V18.0.4

This is a release of the Java integration for Vaadin Components to be used from the Java server side with Vaadin Flow.

Changes in Flow Components from 18.0.3

Changes in vaadin-avatar-flow

  • Chore:
    • ⧉ Increase Web-Component version

Changes in vaadin-crud-flow

  • Fixes:
    • ⧉ Update openRowForEditing to get vaadin-crud-edit based on row.index (#541). PR:545

Changes in vaadin-date-picker-flow vaadin-date-time-picker-flow vaadin-radio-button-flow vaadin-text-field-flow vaadin-time-picker-flow

  • Fixes:

    • ⧉ Fix client side validation overriding (#512). PR:548. Ticket:8848

      The workaround for overriding the client side validation for certain components was causing an unnecessary roundtrip to the server side, which also caused two warnings to be logged by Flow each time a disabled or a readonly component was added to the UI. The warning happened twice since two executeJS calls were enqueued: one immediately, and another when attached. Apparently there was no good reason for this behavior. This fix will only apply the executeJS once when the component is attached and it will not require a separate roundtrip to workaround the client side validation overriding the invalid value because the JS execution is enqueued on the "beforeClientResponse" phase when the server side invalid value has been resolved and can be used in the JS execution. Further improvement would be to move the FieldValidationUtil to its own module and reused from there, but that is left for later (?).

Compatibility

  • This release uses Web Components listed in Vaadin Platform 18.0.4
  • Tested with Vaadin Flow version 5.0.2
Assets 2
Loading