Skip to content

Vaadin Flow 2.5.0.alpha2

Pre-release
Pre-release

Choose a tag to compare

View all tags
@vaadin-bot vaadin-bot released this 08 Feb 12:03
2.5.0.alpha2
7df84a5
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Vaadin Flow 2.5.0.alpha2

Flow 2.5 is a minor release targeted to Vaadin 14.5.

Changes in Flow from 2.5.0.alpha1

  • New Features:

    • Lit Element & TypeScript support + Reading Initial Attribute Values for Templates

      • Using LitTemplate is recommended over PolymerTemplate for doing layouts with HTML and UI logic in Java. It is recommended to use TypeScript for the template and this has been updated to the examples in the documentation.
      • In Flow 2.5+, the initial attribute values in the template are reflected to the server side state when @Id mapping components. This applies to both LitTemplate and PolymerTemplate.
      • More information on the template support in the blog.

    • Routing: URL parameters template feature
      Parameters in the middle of the URL (#2740) and multiple optional parameters (#4213) are now supported, like /order/:id/edit

  • Breaking Changes and Deprecations:

    • Lit Element support related changes

      • The changes in Flow 2.5 do not require changing existing PolymerTemplate based components. In case you have an existing workaround placed for handling the initial attribute values for template-mapped-components, those workarounds should not be needed anymore.

    • Routing: URL parameters template changes

      • BeforeEvent::getForwardTargetType and BeforeEvent::getRerouteTargetParameters methods are deprecated. The methods' javadocs point to the new methods to use instead.
      • RouteRegistry::getRouteLayouts is deprecated, RouteRegistry::getNavigationRouteTarget is recommended to be used instead.
      • UI.getRouter() is now deprecated as a low-level routing API, UI::navigate() methods should be used instead, as a high-level API for routing.
      • com.vaadin.flow.server.startup.RouteTarget has been completely removed. This class was internal and should not have been used by anyone. In case you have been using it, please create an issue describing what you needed it for.

  • Fixes:

    • ⧉ Clear all routes references in ConfigureRoutes. PR:9050

      Clear all routes references in ConfigureRoutes including the RouteModel. (cherry picked from commit 819eb22)

    • ⧉ Importing binary file in frontend file (#9955). PR:9960. Ticket:9926

      Catch MalformedInputException for reading file during import visit for frontend files where file is binary and can not be read as lines.

Assets 2
Loading