vaadin/flow 24.8.0.alpha3

Vaadin Flow 24.8.0.alpha3

on GitHub

Changes since 24.8.0.alpha2

All changes

New features

• Allow forcing Hotswapper to reload the page
  Commit · Pull request · Issue

  By default, on class change, Hotswapper determines the best strategy to refresh the browser page. However, in some situations, a full page reload may be a better option. This change allows forcing Hotswapper to always trigger a full page reload if the vaadin.hotswap.forcePageReload system property is set to true. In addition, the Hotswapper.forcePageReload() method can be called to change the behavior at runtime instead of setting the system property.

• ReactAdapter and element to support jackson
  Commit · Pull request

  Have ReactAdapter and elemnt use jackson. AbstractSinglePropertyField to support jackson type. part of #20741 DeaultRpcDecoder now handles elemental and jackson

Fixes

• Prevent hot-reload failure caused by prepare-frontend task
  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.

• Renavigation to same url
  Commit · Pull request · Issue

  after initial navigation to same route when using postpone

• Clean file-routes if hilla not in use
  Commit · Pull request · Issue

• Add global click handler for navigation
  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.

• Add allowInert support for synchronized properties
  Commit · Pull request · Issue