vaadin/flow 24.4.10

Vaadin Flow 24.4.10

on GitHub

Changes since 24.4.9

All changes

Fixes

• Clear CurrentInstance before invoking new session tasks (#6349) (#20255)
  Commit · Pull request · Issue

  Commands enqueued by VaadinSession.access() in general have nothing to do with each other. The only thing they have in common is they share the same VaadinSession (and, by implication, VaadinService). Therefore, if command №1 invoked UI.setCurrent() and command №2 invokes UI.getCurrent(), command №2 should read null, not the random UI from command №1 that it has nothing to do with.

• Prevent possible error on embedded component disconnect (#20260)
  Commit · Pull request

• Force hotdeploy with hilla (#20251)
  Commit · Pull request

• Resolve route parameters when rerouting and forwardin with query parameters (#20210)
  Commit · Pull request · Issue

• VaadinSessionScopes for all sessions are destroyed when any single session expires #20092 (#20103)
  Commit · Pull request

• Perform server navigation roundtrip only when client side navigation is completed (#20187) (CP: 24.4)
  Commit · Pull request · Issue

• Always fetch reactEnabled from service (#20125) (CP: 24.4)
  Commit · Pull request

• Consider layout prefixes when checking for route and alias paths (#20126)
  Commit · Pull request · Issue

• Allow null response in logout (#20057)
  Commit · Pull request · Issue

  Don't throw NullPointerException in case of null VaadinServletResponse in AuthenticationContext#logout. Tolerate null response better in case when running with @Push(transport = Transport.WEBSOCKET), or when response is null for some other reason. Makes logout also work in WEBSOCKET mode by automatically switching to WEBSOCKET_XHR for one additional request that executes logout.