github vaadin/platform 19.0.9
Vaadin 19.0.9

latest releases: 24.6.0.alpha3, 23.5.10, 24.5.4...
3 years ago

Vaadin 19.0.9

Vaadin consists of a set of web components, a Java web framework, configurable themes, tools and a set of app templates.

This is a maintenance release of Vaadin.
See the full release notes for vaadin 19.0 in GitHub releases, including new features, getting started, supported browsers and other technologies, and migration notes.

Visit vaadin.com to get started.

New and Noteworthy

Here are the highlighted new and improved features in this maintenance release.

Vaadin Flow (6.0.10)

  • Fixes:
    • Add javadocs warning to avoid using ResponseWriter for dirs (#11112). PR:11164

    • Handle concurrent file requests (#11147). PR:11156. Ticket:11144

    • Set routes first into the template (#11107). PR:11126. **Ticket:**psi#26

    • Prevent passing bad character to wp (#11099). PR:11114

      The webpack dev-server does not escape " character, as it is not valid URL. This limitation was not checked when passing request to it via DevModeHandlerImpl.

    • Use x64 version for mac for old nodejs (#11065). PR:11068. Ticket:11060

      Use the x64 package for mac if the installed node version is < 16.0.0 as ARM package is not available before this.

    • Don't serve directories as static files (#11072). PR:11104

      Add check to the resource to see if it is a directory and do not serve if this is the case. Fixe #11047

    • Annotate default error handlers. (#11063) (#11090). PR:11093

      Annotate default error handlers with the new annotaton DefaultErrorHandler so that we can also in add-ons have default handlers that can be overridden by user handlers. Part of vaadin/spring#661 # Conflicts: # flow-server/src/main/java/com/vaadin/flow/router/InternalServerError.java # flow-server/src/main/java/com/vaadin/flow/router/RouteNotFoundError.java

    • Avoid NPE in query params parsing (#11075). PR:11095. Ticket:11019

      A colon ":" in the location will not cause a NPE when parsing query parameters

    • Using a custom RouteRegistry (#11033). PR:11054. Ticket:11022

      Make it possible to create a custom RouteRegistry and add test module for it.

    • Don't update cached extended details inside callback (#11043). PR:11049. Ticket:473

      Makes fetching extended client details work for Multiplatform Runtime.

Flow Components 19.0.9

Changes in vaadin-checkbox-flow

  • Fixes:
    • Disable checkbox after applying value (#994). PR:1713. Ticket:993

Changes in vaadin-date-picker-flow

  • Warranty Fixes:
    • Update date picker overlay after setting I18N settings (#1742) (CP: 19.0). PR:1751. **Tickets:**I18N, 1411

      (cherry picked from commit ec6054541b6fe1df6d40b044dc89059a9d3edbb2)

Changes in vaadin-grid-flow

  • Fixes:

Changes in vaadin-upload-flow

  • Fixes:
    • Prevent NPE with autoUpload=false and multiple files are being uploaded. PR:1788

Webcomponents in Vaadin 19.0.9

Support

vaadin 19 is supported for one month after Vaadin 20 has been released. The latest LTS (long term support) version is Vaadin 14. More details of our release model are available on our roadmap page.

Vaadin also provides commercial support and warranty.

Getting Started with Vaadin

App starters

The best way to get started with Vaadin is to go to https://start.vaadin.com and configure your new application by setting up your views, entities, styles, and the technology stack you’re interested in.

For the full list of how to get started go to the GitHub releases.

Reporting Issues

We appreciate if you try to find the most relevant repository to report the issue in. If it is not obvious which project to add issues to, you are always welcome to report any issue at https://github.com/vaadin/platform/issues.

A few rules of thumb will help you and us in finding the correct repository for the issue:

  1. Bug tickets and enhancement requests that are specific to a certain Vaadin component should be posted in the component's Web Component repostory (e.g. https://github.com/vaadin/vaadin-button for Button).
  2. Issues that are not component-specific (e.g. requests for new components) or encompass multiple components should be posted in vaadin-flow-components repository.
  3. If you encounter an issue with Flow which does not seem to be related to a specific component, the problem is likely in Flow itself. The Flow repository is https://github.com/vaadin/flow
  4. If you encounter an issue with Designer, the repository is https://github.com/vaadin/designer
  5. If you encounter an issue with TestBench, the repository is https://github.com/vaadin/testbench

Don't miss a new platform release

NewReleases is sending notifications on new releases.