Vaadin Flow Components V19.0.0.alpha2
Pre-release
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
Changes in vaadin-charts-flow
-
Breaking Changes:
-
Chore:
- ⧉ Increase Web-Component version
Changes in vaadin-combo-box-flow
Changes in vaadin-confirm-dialog-flow
Changes in vaadin-cookie-consent-flow
Changes in vaadin-crud-flow
-
Breaking Changes:
-
Fixes:
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:
Changes in vaadin-grid-pro-flow
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
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