Releases: vaadin/flow
Vaadin Flow 24.7.0.alpha5
Changes since 24.7.0.alpha4
New features
-
Add support for OAuth2 logout configuration
Commit · Pull request · IssueImproves setOAuth2LoginPage method in order to configure an OIDC logout succes shandler capable of handling redirection for UIDL requests. Post logout URL is by default the application root, but a method overload allows to specify a custom URL.
Fixes
-
Validate downloaded node
Commit · Pull request · IssueValidate downloaded node against the provided sha256 hash.
-
Remove broken node archive
Commit · Pull requestIf archive extraction throws remove arcive to next time re-download. In cases where the archive can be corrupt remove file.
Vaadin Flow 24.7.0.alpha4
Changes since 24.7.0.alpha3
New features
- React 19 behind a feature flag
Commit · Pull request
Fixes
-
ReactRouterOutlet interferes with layout
Commit · Pull request -
Parse bot user agents
Commit · Pull request · IssueAdd parsing for byte spider and duck duck bot user agents.
Vaadin Flow 24.6.2
No changes since 24.6.1
Vaadin Flow 24.5.11
Changes since 24.5.10
Fixes
-
Close opened input stream. (#20772)
Commit · Pull request · IssueImageIO.read does not close the input stream. Close it after use.
Vaadin Flow 24.4.16
No changes since 24.4.15
Vaadin Flow 24.6.1
Changes since 24.6.0
Fixes
-
Parse bot user agents (#20785)
Commit · Pull request · IssueAdd parsing for byte spider and duck duck bot user agents.
-
Close opened input stream. (#20772)
Commit · Pull request · IssueImageIO.read does not close the input stream. Close it after use.
-
Trigger refresh on hotswap only for redefined classes (#20684)
Commit · Pull request · Issues 20680, 20681Prevent hotswapper to trigger a refresh when the classes are loaded for the first time. Refreshing a view should make sense only if a project class has been modified. The only exception is auto layout classes, that must be applied even if they are not directly references in the component tree.
-
Re-build production bundle if index.html changes (#20729)
Commit · Pull request · IssueStores index.html hash in stats.json and forces production bundle to be re-built if file contents have changed. Changes to index.html do not trigger a dev bundle re-generation since in dev mode the file is served directly from the frontend folder.
Vaadin Flow 24.7.0.alpha3
Changes since 24.7.0.alpha2
New features
-
Add feature flag for Card
Commit · Pull request
Fixes
-
Close opened input stream.
Commit · Pull request · IssueImageIO.read does not close the input stream. Close it after use.
-
Trigger refresh on hotswap only for redefined classes
Commit · Pull request · Issues 20680, 20681Prevent hotswapper to trigger a refresh when the classes are loaded for the first time. Refreshing a view should make sense only if a project class has been modified. The only exception is auto layout classes, that must be applied even if they are not directly references in the component tree.
Vaadin Flow 24.5.10
Changes since 24.5.9
Fixes
-
Trigger refresh on hotswap only for redefined classes (#20684)
Commit · Pull request · Issues 20680, 20681Prevent hotswapper to trigger a refresh when the classes are loaded for the first time. Refreshing a view should make sense only if a project class has been modified. The only exception is auto layout classes, that must be applied even if they are not directly references in the component tree.
-
Re-build production bundle if index.html changes (#20729)
Commit · Pull request · IssueStores index.html hash in stats.json and forces production bundle to be re-built if file contents have changed. Changes to index.html do not trigger a dev bundle re-generation since in dev mode the file is served directly from the frontend folder.
-
Handle logout from a background thread (#20688)
Commit · Pull requestAllows AuthenticationContext.logout feature to be used from a background thread, handling the missing request by forcing the client to make an additional request. Applies the same logic used to support logout when using PUSH with websocket transport. References #11026
-
Fix role checking when using websocket push (#20679)
Commit · Pull requestWhen using PUSH with websocket transport, the atmosphere wrapped request can be a no-op implementation whose isUserInRole method alwasy returns false, causing, for example, wrong access checking during navigation. This change falls back to Spring Securty for role checking when PUSH transport is websocket. It also fixes some tests in order to propagate the Spring Security context when starting Thread that perform UI operations. References psi#123 Part of #11026
-
Catch exceptions from detach calls (#20656)
Commit · Pull request -
Ensure requestEnd clears Vaadin thread locals (#20687)
Commit · Pull requestMakes sure that Vaadin thread locals are cleared even if something fails durung requestEnd execution. It also wraps Vaadin interceptors execution in a try/catch block to ensure all of them are invoked and that potential failures does not affect the continuation of requestEnd method.
-
Fix redirect URL for PUSH with websocket transport (#20666)
Commit · Pull request · Issue -
Appended path on fast navigate (#20673)
Commit · Pull request · IssueWhen navigating in quick succession check that path starts with / as else react wll append to current url.
-
Wrap UI closing to catch exceptions (#20645)
Commit · Pull request · IssueWhen session destroy is triggered, wraps each UI close/detach to catch exceptions, making sure session destroy listeners are called.
-
Add React Router future flags for flow auto-generated routes file (#20641)
Commit · Pull request -
Service destroy listener exceptions (#20622)
Commit · Pull requestRelated to #20577
Vaadin Flow 24.4.15
Changes since 24.4.14
Fixes
-
Re-build production bundle if index.html changes (#20729)
Commit · Pull request · IssueStores index.html hash in stats.json and forces production bundle to be re-built if file contents have changed. Changes to index.html do not trigger a dev bundle re-generation since in dev mode the file is served directly from the frontend folder.
-
Handle logout from a background thread (#20688)
Commit · Pull requestAllows AuthenticationContext.logout feature to be used from a background thread, handling the missing request by forcing the client to make an additional request. Applies the same logic used to support logout when using PUSH with websocket transport. References #11026
-
Fix role checking when using websocket push (#20679)
Commit · Pull requestWhen using PUSH with websocket transport, the atmosphere wrapped request can be a no-op implementation whose isUserInRole method alwasy returns false, causing, for example, wrong access checking during navigation. This change falls back to Spring Securty for role checking when PUSH transport is websocket. It also fixes some tests in order to propagate the Spring Security context when starting Thread that perform UI operations. References psi#123 Part of #11026
-
Catch exceptions from detach calls (#20656)
Commit · Pull request -
Ensure requestEnd clears Vaadin thread locals (#20687)
Commit · Pull request -
Fix redirect URL for PUSH with websocket transport (#20666)
Commit · Pull request · Issue -
Wrap UI closing to catch exceptions (#20645)
Commit · Pull request · IssueWhen session destroy is triggered, wraps each UI close/detach to catch exceptions, making sure session destroy listeners are called.
-
Service destroy listener exceptions (#20622)
Commit · Pull requestRelated to #20577
-
Enforce plugin-required dependencies and log incompatibilities (#20601)
Commit · Pull request · IssueThe Flow Maven Plugin uses a class loader that combines project and plugin dependencies to ensure class scanning happens on runtime artifacts. However, plugin execution may fail if the project defines dependency versions incompatible with those used by the plugin. This change enforces the use of plugin-defined versions for certain dependencies not directly used by Flow at runtime. Additionally, it logs potential incompatibilities for other dependencies if the build fails.
Vaadin Flow 2.11.4
Changes since 2.11.3
Fixes
-
Do not mistakenly run 2 npm installs
Commit · Pull request · Issue -
Ensure requestEnd clears Vaadin thread locals (#20687)
Commit · Pull requestMakes sure that Vaadin thread locals are cleared even if something fails durung requestEnd execution. It also wraps Vaadin interceptors execution in a try/catch block to ensure all of them are invoked and that potential failures does not affect the continuation of requestEnd method.