Vaadin Flow 24.6.0.beta8

Changes since 24.6.0.beta7

All changes

Fixes

• Add React Router future flags for flow auto-generated routes file
  Commit · Pull request

• Service destroy listener exceptions (#20622)
  Commit · Pull request

  Related to #20577

• Remove timeout for browser websocket connection for Vite (#20611)
  Commit · Pull request

Vaadin Flow 24.5.9

Changes since 24.5.8

All changes

Fixes

• Remove timeout for browser websocket connection for Vite (#20611)
  Commit · Pull request

• Enforce plugin-required dependencies and log incompatibilities (#20601)
  Commit · Pull request · Issue

  The 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 24.6.0.beta7

Changes since 24.6.0.beta6

All changes

Fixes

• Enforce plugin-required dependencies and log incompatibilities (#20601)
  Commit · Pull request · Issue

  The 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 24.6.0.beta6

Changes since 24.6.0.beta5

All changes

Fixes

• Remove modal component on route refresh (#20540)
  Commit · Pull request · Issue

  Modal components attached to the UI were not removed or replaced during self-navigation triggered by a route refresh. This change updates navigation handler to ensure modal components are removed and adds a new navigation trigger for route refresh to differentiate programmatic navigations (e.g., forward actions). It also modifies Hotswapper to require a full chain refresh when modal components are present.

• Add vite-ping subprotocol to Vite websocket proxy (#20578)
  Commit · Pull request · Issue

Vaadin Flow 24.5.8

Changes since 24.5.7

All changes

Fixes

• Remove modal component on route refresh (#20540)
  Commit · Pull request · Issue

  Modal components attached to the UI were not removed or replaced during self-navigation triggered by a route refresh. This change updates navigation handler to ensure modal components are removed and adds a new navigation trigger for route refresh to differentiate programmatic navigations (e.g., forward actions). It also modifies Hotswapper to require a full chain refresh when modal components are present.

• Include all component tracker locations (#20568)
  Commit · Pull request

  Some filtering was already earlier moved to Copilot and handling everything in the same place is easier

• Compute unique key for artifact (#20551)
  Commit · Pull request

  Computes a unique key for maven artifacts when collecting dependencies for the Flow maven plugin isolated classloader.

• Prevent hotswap failure if class is not found (#20549)
  Commit · Pull request

  References #20389

Vaadin Flow 24.6.0.beta5

Changes since 24.6.0.beta4

All changes

Fixes

• Include all component tracker locations (#20568)
  Commit · Pull request

  Some filtering was already earlier moved to Copilot and handling everything in the same place is easier

Vaadin Flow 24.6.0.beta4

Changes since 24.6.0.beta3

All changes

Fixes

• Compute unique key for artifact (#20551)
  Commit · Pull request

  Computes a unique key for maven artifacts when collecting dependencies for the Flow maven plugin isolated classloader.

• Prevent hotswap failure if class is not found (#20549)
  Commit · Pull request

  References #20389

• Multiple fast navigate calls (#20446)
  Commit · Pull request · Issue

  Fix issue where a slow connection and fast navigate calls throws exception due to faulty blocker state change.

Vaadin Flow 24.4.14

Changes since 24.4.13

All changes

Fixes

• Compute unique key for artifact (#20551)
  Commit · Pull request

  Computes a unique key for maven artifacts when collecting dependencies for the Flow maven plugin isolated classloader.

• Multiple fast navigate calls (#20446)
  Commit · Pull request · Issue

  and fast navigate calls throws exception due to faulty blocker state change. Add test view for manual testing. Test script doesn't fail on double click.

Vaadin Flow 24.5.7

Changes since 24.5.6

All changes

Fixes

• Vaadin/router added with react-router (#20522)
  Commit · Pull request · Issue

  Exclude vaadin/router when runing in react mode. Without exclusion vaadin/router gets added from the vaadin-core.json package in platform.

• Multiple fast navigate calls (#20446)
  Commit · Pull request · Issue

  and fast navigate calls throws exception due to faulty blocker state change. Add test view for manual testing. Test script doesn't fail on double click. ---------

Vaadin Flow 24.5.6

Changes since 24.5.5

All changes

Fixes

• Exclude project maven dependencies from isolated class loader (#20523)
  Commit · Pull request

  If the user project directly or transitively depends on maven artifacts, mojos can fail at runtime because of Maven API loaded from both isolated class loader and maven.api realm. This change prevents maven artifacts from being added to the isolated class loader.

• Fix class and resource loading in maven plugin (#20465)
  Commit · Pull request · Issues 19616, 19009, 20385

  Run Flow mojos using an isolated class loader that includes both project and plugin dependencies, with project dependencies taking precedence. This ensures that classes are always loaded from the same class loader at runtime, preventing errors where a class might be loaded by the plugin's class loader while one of its parent classes is only available in the project’s class loader (see #19616). Additionally, this approach prevents the retrieval of resources from plugin dependencies when the same artifact is defined within the project (see #19009). This refactoring also introduces caching for ClassFinder instances per execution phase, allowing multiple goals configured for the same phase to reuse the same ClassFinder. It also removes the need to instantiate a ClassFinder solely for Hilla class checks, reducing the number of scans performed during the build.

• Move blocking calls outside session lock (#19938) (#20475)
  Commit · Pull request

  Move blocking calls outside session lock (#19938)

• Client route autolayout should have parent layouts chain (#20511)
  Commit · Pull request · Issue

  When having a client route for server layout the layout parent routes should be collected.

• Do not try to refresh app while it is initializing (#20504)
  Commit · Pull request

  When the app is bootstrapping, it only contains initializing, isActive and productionMode. We should not call sendEventMessage at this point or might cause Uncaught TypeError: l.sendEventMessage is not a function. This is unlikely to happen in many real world scenarios but happens in Copilot tests

• Fix ServletFileUpload header encoding (#20480) (CP: 24.5)
  Commit · Pull request · Issue

• Refresh locations arrays also (#20483)
  Commit · Pull request