vaadin/flow 24.4.0.alpha4

Vaadin Flow 24.4.0.alpha4

on GitHub

Changes since 24.4.0.alpha3

All changes

New features

• Make it possible to controll clean-frontend
  Commit · Pull request

  Add options object that can be used to controll what is removed/cleaned in the clean-frontend goal. By deault everything is done.

• Write source information for React components defined in the project
  Commit · Pull request

  When transpiling tsx/jsx to ts/js, Babel writes the source information for where components are used. This adds the information about where components are defined.

• SBOM generation
  Commit · Pull request

Fixes

• Consider local npm packages in bundle validation
  Commit · Pull request · Issue

  If a project package.json contains references to local npm pacakges instead of parsable version, the bundle validation fails. This change update the version check in bundle validation to accept also local packages. For those packages, a bundle re-creation is triggered only if the reference in package.json does not match the one in the stats.

• Include translation files in Spring native compile hints
  Commit · Pull request · Issue

• Allow moving node to another tree after removeFromTree call
  Commit · Pull request · Issue

  Enables moving a component to another UI by just calling Element.removeFromTree() and then adding the component to the other UI.

• No serverSideRoutes check if no Routes
  Commit · Pull request

  Do not check for the serverSideRoutes in routes.tsx in react mode if no @Route annotated Flow routes found. Make more readable.

• Binder validation fixes
  Commit · Pull request · Issues 18163, 4988, 17515

  Changes: - Once Binder.handleFieldValueChange runs for a binding when readBean was used, the whole binder will be silently validated also. BinderValidationStatusHandler is called like before (only contains status from changed binding), but StatusChangeEvent is now fired considering all bindings and if possible bean validators as well. - Once Binder.handleFieldValueChange runs for a binding when setBean was used, doWriteIfValid will validate all bindings, not only the changed ones. This prevents writing an invalid bean in cases where one or more of the initial values are in invalid state (but not marked as such since setBean resets validation status), but they have not been changed from their initial value(s). Calling setAsRequiredEnabled with a changed value no longer triggers validation, since that validation is now handled elsewhere when needed as stated above. Minor Javadoc fixes, trying to align Javadocs with code.

• Pass a mutable copy of routes array into React function
  Commit · Pull request

  This should fix the TS compilation error in Hilla test module, saying frontend/generated/flow/Flow.tsx(264,39): error TS2345: Argument of type 'readonly ViewRouteObject[]' is not assignable to parameter of type 'ViewRouteObject[]'. The type 'readonly ViewRouteObject[]' is 'readonly' and cannot be assigned to the mutable type 'ViewRouteObject[]'. by converting an immutable routes array into mutable copy.