Vaadin Flow Components V14.5.0.alpha1

Vaadin Flow Components 14.5.0.alpha1

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 14.4.0

Changes in vaadin-avatar-flow

• New Features:
  • ⧉ Backported avatar to 14.5. PR:552. Ticket:416

Changes in vaadin-grid-flow

• New Features:

  • ⧉ Add API to control nested properties null behavior (#217). PR:345. Ticket:8891

    New API, setNestedNullBehavior, controls whether an exception is thrown or not when facing nested null values.

Compatibility

• This release use Web Components listed in Vaadin Platform 14.5.0.alpha1
• Tested with Vaadin Flow version 6.0.0.alpha5

Vaadin Flow Components V14.4.7

Vaadin Flow Components V14.4.7

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 14.4.6

Changes in vaadin-crud-flow

• Fixes:

  • ⧉ Replace select(null) with deselectAll() (#189). PR:567. Ticket:1014

    It is SelectionModel.java and inherited select() there. Grid's select is direct call to that. Grid's JavaDoc has dropped the notion of null not ok. /** * */ void select(T item);

Changes in vaadin-grid-flow

• Warranty Fixes:
  • ⧉ Clear subchildren when refreshing item (#588). PR:597. Ticket:1819

Changes in vaadin-notification-flow

• Chore:
  • ⧉ Increase Web-Component version
  • ⧉ Increase Web-Component version

Compatibility

• This release use Web Components listed in Vaadin Platform 14.4.7
• Tested with Vaadin Flow version 2.4.6

Vaadin Flow Components V19.0.0.alpha5

Vaadin Flow Components V19.0.0.alpha5

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 19.0.0.alpha4

Changes in vaadin-grid-flow

• Fixes:
  • ⧉ Clear subchildren when refreshing item. PR:588. Ticket:1819

Compatibility

• This release use Web Components listed in Vaadin Platform 19.0.0.alpha5
• Tested with Vaadin Flow version 6.0.0.alpha5

Vaadin Flow Components V19.0.0.alpha4

Vaadin Flow Components V19.0.0.alpha4

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 19.0.0.alpha3

Changes in vaadin-accordion-flow

• Fixes:
  • ⧉ Added HasStyle interface to the Accordion, AccordionPanel and Details components.. PR:569. Tickets:564. add HasStyle interface to the Accordion AccordionPanel and Details components.
  • ⧉ Add a missing dependency for the Accordion integration tests.

Changes in vaadin-crud-flow

• Fixes:

  • ⧉ Replace select(null) with deselectAll(). PR:189. Ticket:1014

    It is SelectionModel.java and inherited select() there. Grid's select is direct call to that. Grid's JavaDoc has dropped the notion of null not ok. /** * */ void select(T item);

Changes in vaadin-details-flow

• Fixes:
  • ⧉ Added HasStyle interface to the Accordion, AccordionPanel and Details components.. PR:569. **Tickets:**add, HasStyle, interface, to, the, Accordion, AccordionPanel, and, Details, components., 564
  • ⧉ Add a missing dependency for the Accordion integration tests.

Changes in vaadin-notification-flow

• Chore:
  • ⧉ Increase Web-Component version

Compatibility

• This release use Web Components listed in Vaadin Platform 19.0.0.alpha4
• Tested with Vaadin Flow version 6.0.0.alpha4

Vaadin Flow Components V18.0.5

Vaadin Flow Components V18.0.5

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.4

Changes in vaadin-grid-flow

• Fixes:
  • ⧉ Revert ensure first page is loaded; ignore test till fixed (#551). PR:560

Compatibility

• This release use Web Components listed in Vaadin Platform 18.0.5
• Tested with Vaadin Flow version 5.0.2

Vaadin Flow Components V14.4.6

Vaadin Flow Components V14.4.6

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 14.4.5

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) (CP: 14.4). PR:549. Ticket:8848

  • ⧉ Fix client side validation overriding. PR:512

    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 (?).

  • ⧉ Use previous API to check if it is attached

Changes in vaadin-grid-flow

• Fixes:
  • ⧉ Revert ensure first page is loaded; ignore test till fixed (#551). PR:563

Compatibility

• This release use Web Components listed in Vaadin Platform 14.4.6
• Tested with Vaadin Flow version 2.4.4

Vaadin Flow Components V19.0.0.alpha3

Vaadin Flow Components V19.0.0.alpha3

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

There are no Changes in Flow Components since 19.0.0.alpha2

Compatibility

• This release use Web Components listed in Vaadin Platform 19.0.0.alpha3
• Tested with Vaadin Flow version 6.0.0.alpha4

Vaadin Flow Components V19.0.0.alpha2

Vaadin Flow Components V19.0.0.alpha2

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 19.0.0.alpha1

Changes in vaadin-board-flow

• Breaking Changes:
  • ⧉ Change CVAL3 to CVDL4 for PRO components. PR:511

Changes in vaadin-charts-flow

• Breaking Changes:

  • ⧉ Change CVAL3 to CVDL4 for PRO components. PR:511

• Chore:

  • ⧉ Increase Web-Component version

Changes in vaadin-combo-box-flow

• Breaking Changes:
  • ⧉ Change CVAL3 to CVDL4 for PRO components. PR:511

Changes in vaadin-confirm-dialog-flow

• Breaking Changes:
  • ⧉ Change CVAL3 to CVDL4 for PRO components. PR:511

Changes in vaadin-cookie-consent-flow

• Breaking Changes:
  • ⧉ Change CVAL3 to CVDL4 for PRO components. PR:511

Changes in vaadin-crud-flow

• Breaking Changes:

  • ⧉ Change CVAL3 to CVDL4 for PRO components. PR:511

• Fixes:

  • ⧉ Update openRowForEditing to get vaadin-crud-edit based on row.index. PR:541

Changes in vaadin-date-picker-flow

• Fixes:

  • ⧉ Fix client side validation overriding. PR:512. 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 (?).

Changes in vaadin-date-time-picker-flow

• Fixes:

  • ⧉ Fix client side validation overriding. PR:512. 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 (?).

Changes in vaadin-grid-flow

• Fixes:
  • ⧉ Revert ensure first page is loaded; ignore test till fixed. PR:551
  • ⧉ Remove redundant sorter renderer. PR:515
  • ⧉ Ensure first page is loaded; sorting not breaking on hidden grid. PR:529

Changes in vaadin-grid-pro-flow

• Breaking Changes:
  • ⧉ Change CVAL3 to CVDL4 for PRO components. PR:511

Changes in vaadin-radio-button-flow

• Fixes:

  • ⧉ Fix client side validation overriding. PR:512. 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 (?).

Changes in vaadin-rich-text-editor-flow

• Breaking Changes:
  • ⧉ Change CVAL3 to CVDL4 for PRO components. PR:511

Changes in vaadin-text-field-flow

• Fixes:

  • ⧉ Fix client side validation overriding. PR:512. 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 (?).

Changes in vaadin-time-picker-flow

• Fixes:

  • ⧉ Fix client side validation overriding. PR:512. 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 use Web Components listed in Vaadin Platform 19.0.0.alpha2
• Tested with Vaadin Flow version 6.0.0.alpha4

Vaadin Flow Components V18.0.4

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

Vaadin Flow Components V14.4.5

Vaadin Flow Components V14.4.5

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 14.4.4

Changes in vaadin-combo-box-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:542

Changes in vaadin-date-time-picker-flow

• Fixes:

  • ⧉ Use right value at getErrorMessage (#507). PR:510. Ticket:60

• Chore:

  • ⧉ Increase Web-Component version

Changes in vaadin-grid-flow

• Fixes:
  • ⧉ Remove redundant sorter renderer. PR:535. Ticket:1841.
  • ⧉ Ensure first page is loaded; sorting not breaking on hidden grid (cp #529). PR:531
  • ⧉ Prevent exception in gridConnector. PR:462

Changes in vaadin-icons-flow

• Chore:
  • ⧉ Increase Web-Component version

Changes in vaadin-menu-bar-flow

• Chore:
  • ⧉ Increase Web-Component version

Changes in vaadin-radio-button-flow

• Fixes:

  • ⧉ Disable client side validation (#461) (CP:14.4). PR:492. Ticket:179

    - Disable client side validation - Validation from Binder will happen upon Binder#validate() or if the field binding uses withValidator

  • ⧉ Allow null items in RadioButtonGroup (#514). PR:519

Changes in vaadin-time-picker-flow

• Chore:
  • ⧉ Increase Web-Component version

Compatibility

• This release use Web Components listed in Vaadin Platform 14.4.5
• Tested with Vaadin Flow version 2.4.4