vaadin/flow 24.6.9

Vaadin Flow 24.6.9

on GitHub

Changes since 24.6.8

All changes

Fixes

• Prevent hot-reload failure caused by prepare-frontend task (#21174)
  Commit · Pull request · Issues 20831, 19748

  If the prepare-frontend task is invoked while the Vaadin application is running, it may happen that some generated files are mistakenly removed, causing the frontend compilation to fail and sometimes an infinite reload loop. This happens, for example, in Hilla projects based on Gradle and IntelliJ IDEA: when the IDE compiles a class, it runs Gradle, and the vaadinPrepareFrontend task is executed. Some generated files are then deleted for two reasons: Hilla is not detected because the check is done during the Gradle configuration phase, and it uses the plugin class loader, which does not have references to the project dependencies. The TaskRemoveOldFrontendGeneratedFiles is executed, but it fails to compare non-normalized paths. This change fixes the two issues by detecting Hilla from the project dependencies and normalizing paths before comparison. (cherry picked from commit 5fe0e3b)

• Renavigation to same url (#21170)
  Commit · Pull request · Issue

  After initial navigation to same route when using postpone.

• Add global click handler for navigation (#20990)
  Commit · Pull request · Issue

  When using React router, clicks on anchors are intercepted only if Flow client has been initialized. In Hilla or hybrid application, if a Flow view is never navigated, clicking on such links cause the browser to reload the page instead of navigating to the expected view. This change registers a global click handler that intercepts click events and triggers a router navigation if necessary. The new behavior is aligned with vaadin-router.