vaadin/flow 24.6.0.alpha2

Vaadin Flow 24.6.0.alpha2

on GitHub

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