vaadin/flow 24.0.0.beta1

Vaadin Flow 24.0.0.beta1

on GitHub

Changes since 24.0.0.alpha17

All changes

New features

• Allow every component to have styles
  Commit · Pull request

  All components are capable of having class names yet you must remember to implement HasStyle every time you create a new component or the class API is missing. The only known exception is a text node which cannot have classes. It is fine if this edge case, which is almost never used, throws an exception from the API

• Register @Route classes for Spring native automatically
  Commit · Pull request

Fixes

• Use correct SecurityContextRepository for stateless authentication
  Commit · Pull request · Issue

  The shared objects need to be available when other configurers are run and because of spring-projects/spring-security#12579 a workaround is needed to actually apply the correct SecurityContextRepository

• Fix problems in Hilla native compilation
  Commit · Pull request

  Caused by resource or classes not always being available

• Do not perform type checking for TS files from jar files
  Commit · Pull request · Issue

  The TS files that come from JAR files are not under control of the project developer so enforcing project TS rules on them does not make sense. This is similar to "skipLibCheck" used for TS files that are in node_modules.

Known issues

• Embedded web components are not rendered properly
  Issue

  To workaround this issue, enable Vite development server mode (default development mode in Vaadin 23) with a property vaadin.frontend.hotdeploy=true in application.properties (for Spring-based applications) or by setting vaadin.frontend.hotdeploy to true in the vaadin-maven-plugin or as a system property (for non-Spring applications). This will be fixed in the next beta releases.