vaadin/flow 2.6.0

Vaadin Flow 2.6.0

on GitHub

Vaadin Flow 2.6.0

Flow 2.6 is a minor release for Vaadin 14.6.

New Features

Custom Theme

The Custom Theme is a simplified theming system that works for all Vaadin applications and enables developers to

• Define customised themes based on the Lumo theme.
• Use in-app resources such as style sheets, fonts, background images, etc. easily into the custom theme.
• Have multiple theme folders and enable them just by addressing those folder name in @theme annotation.
• Apply CSS automatically on any components just by putting the css files into a specific folder inside the theme.
• Use resources such as CSS, Fonts, images, etc. from npm dependencies (node_modules).
• Package custom themes into reusable themes and use them in other applications.
• Inherit from other custom themes as the parent theme.

Read more about Custom Theme in Vaadin documentation.

Small enhancements

• ⧉ Allow creation of Text and Element from nullable text content (#10434). PR:10499. Ticket: 10355
• ⧉ Allow spaces in addClassNames arguments array. PR:10354. Ticket: 10353
• ⧉ Add API to Binder for converting back to presentation
  It is possible to set Binder to convert value back to representation and write back to field when changed and validation passes. This ensures correct formatting of the value when a converter is used. The default behavior is not changed for Vaadin 14.6, but starting from Vaadin 20 the value is written back by default. Some applications might have workarounds in place for this and can now remove them. (cherry picked from commit 43871ff)

List of all changes in 2.6.0 from 2.5.4

Changes in Flow from 2.6.0.rc1

• Fixes:

  • ⧉ Enable use of external css using @import (#10953). PR:10964. Ticket:10228

    Add fix for using a external css file by having the @import url(...) in a css file. Also supports imports with media queries.

  • ⧉ Always update webpack.generated.js (#10934). PR:10941. Ticket:10932

    webpack.generated.js should always be generated as there are some paths that may change if the project directory changes.

  • ⧉ Allow empty segments at start (#10921) (#10938). PR:10943. Ticket:10729

    # Conflicts: # flow-server/src/main/java/com/vaadin/flow/router/BeforeEvent.java

  • ⧉ Log limitation of adding new styles while switching themes (#10894). PR:10930. Ticket:10680

    If there are more than one theme available in themes folder, user can switch between them in development mode by changing the name of the theme in @theme. As having a watch for adding new styles in component folder is 'static', at least a log about this limitation is needed.

  • ⧉ Include flow-dnd module to flow-bom (#10911). PR:10925

  • ⧉ Upgrade to LitElement 2.5.1 and lit-html 1.4.1 (#10912) (CP: 2.6). PR:10917

  • ⧉ Include flow-dnd module to flow-bom (#10911). PR:10915

  • ⧉ Use trimmed line in imports rewrite. PR:10897. Ticket:10896

• ⧉ All changes