Vaadin Flow 24.3.21

No changes since 24.3.20

Vaadin Flow 24.6.0.alpha2

Changes since 24.6.0.alpha1

All changes

New features

• Fire an event when all hotswap operations have completed
  Commit · Pull request
• Enable easier override for SpringServlet
  Commit · Pull request · Issue

Fixes

• Import parent theme lumoImports in dev bundle mode (#20325)
  Commit · Pull request · Issue

  Adds missing css imports for parent theme when given in parent theme.json with lumoImports property and running with dev bundle.

• Remove tokenFile after production build
  Commit · Pull request

  Clean the token file after production build/execution to not make ide app execution run app in production mode. Closes #20294

• Make push work with strict CSP
  Commit · Pull request

• Prevent Optional capture in serializable predicate
  Commit · Pull request

  Optional is not serializable, so capturing it into a SerializablePredicate will prevent serialization to succeed.

• Find file-routes.json in dev bundle
  Commit · Pull request · Issue

• Client route collisions
  Commit · Pull request

  collision to not take into account client layouts as they are not route targets.

• Add types to fix some TS warnings in vite.generated.ts
  Commit · Pull request

• Refresh items after changing filtering or sorting with DataViews
  Commit · Pull request

• Use capture for dragLeave
  Commit · Pull request

• Support client route parameters in auto layout path matching
  Commit · Pull request · Issue

  Improves navigation path matching with client route templates. Adds support for matching with route parameters to find automatic Flow main layout for client routes.

• Update default npm version
  Commit · Pull request

  Update default npm version to match the version used by node 22.10.0

• Check for client route conflicts
  Commit · Pull request · Issue

• Clear CurrentInstance before invoking new session tasks (#6349)
  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
  Commit · Pull request

Vaadin Flow 24.5.3

Changes since 24.5.2

All changes

New features

• Fire an event when all hotswap operations have completed (#20364)
  Commit · Pull request

Fixes

• Remove tokenFile after production build (#20346)
  Commit · Pull request

  Clean the token file after production build/execution to not make ide app execution run app in production mode. Closes #20294

• Make push work with strict CSP (#20342)
  Commit · Pull request

• Import parent theme lumoImports in dev bundle mode (#20325)
  Commit · Pull request · Issue

  Adds missing css imports for parent theme when given in parent theme.json with lumoImports property and running with dev bundle.

• Prevent Optional capture in serializable predicate (#20360)
  Commit · Pull request

  Optional is not serializable, so capturing it into a SerializablePredicate will prevent serialization to succeed.

• Find file-routes.json in dev bundle (#20324)
  Commit · Pull request · Issue

Vaadin Flow 24.4.11

Changes since 24.4.10

All changes

New features

• Enable easier override for SpringServlet (#20276)
  Commit · Pull request · Issue

Fixes

• Import parent theme lumoImports in dev bundle mode
  Commit · Pull request · Issue

  Adds missing css imports for parent theme when given in parent theme.json with lumoImports property and running with dev bundle.

• Prevent Optional capture in serializable predicate (#20360)
  Commit · Pull request

  Optional is not serializable, so capturing it into a SerializablePredicate will prevent serialization to succeed.

• Add types to fix some TS warnings in vite.generated.ts (#20270)
  Commit · Pull request

• Use capture for dragLeave (#20291)
  Commit · Pull request

Vaadin Flow 23.5.8

Changes since 23.5.7

All changes

Fixes

• Prevent Optional capture in serializable predicate (#20360)
  Commit · Pull request

  Optional is not serializable, so capturing it into a SerializablePredicate will prevent serialization to succeed.

• Use capture for dragLeave (#20291)
  Commit · Pull request

Vaadin Flow 24.3.20

Changes since 24.3.19

All changes

Fixes

• Prevent Optional capture in serializable predicate (#20360)
  Commit · Pull request

  Optional is not serializable, so capturing it into a SerializablePredicate will prevent serialization to succeed.

• Add types to fix some TS warnings in vite.generated.ts (#20270)
  Commit · Pull request

• Use capture for dragLeave (#20291)
  Commit · Pull request

Vaadin Flow 24.5.2

Changes since 24.5.1

All changes

Fixes

• Client route collisions (#20327)
  Commit · Pull request

  collision to not take into account client layouts as they are not route targets.

• Add types to fix some TS warnings in vite.generated.ts (#20270)
  Commit · Pull request

Vaadin Flow 24.5.1

Changes since 24.5.0

All changes

New features

• Enable easier override for SpringServlet (#20276)
  Commit · Pull request · Issue

Fixes

• Use capture for dragLeave (#20291)
  Commit · Pull request

• Support client route parameters in auto layout path matching (#20284)
  Commit · Pull request · Issue

  Improves navigation path matching with client route templates. Adds support for matching with route parameters to find automatic Flow main layout for client routes.

• Check for client route conflicts (#20188)
  Commit · Pull request · Issue

• 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

Vaadin Flow 24.4.10

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.

Vaadin Flow 24.3.19

Changes since 24.3.18

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.

• Resolve route parameters when rerouting and forwarding with query parameters (#20210) (CP: 24.3)
  Commit · Pull request · Issue

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

• Allow null response in logout (#20057) (CP: 24.3)
  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.