Vaadin Flow 2.6.0.rc1

Vaadin Flow 2.6.0.rc1

Changes in Flow from 2.6.0.beta2

• Fixes:

  • ⧉ Backport 'Inject Lumo CSS also into shadow roots' to 2.6. PR:10836. Ticket:9767

    Adds support for "lumoImports": ["color", "typography", "badge", ... ] to theme.json to override the default ["color", "typography"] If you do not have an application theme specified, Lumo imports are injected by generated-flow-imports.js like before. If you have an application theme, Lumo imports are injected as part of applying the theme. In both cases, Lumo imports are added to the beginning of so they are considered before any other styles, such as @CssImport:ed stylesheets. This allows overriding Lumo CSS rules no matter how you add the CSS.

  • ⧉ Upgrade to LitElement 2.5.0 and lit-html 1.4.0 (#10874). PR:10880. Ticket:10826

  • ⧉ Watch component folders in parent themes (#10834). PR:10884. Ticket:9948

    Adds parent themes component folders to be watched by webpack.

  • ⧉ Adapt warning message to 2.6. PR:10830

  • ⧉ Use global node and tools if they are available first (#10753). PR:10770. Ticket:9863

  • ⧉ Warn to delete component CSS with theme generated in one run (#10779). PR:10827. Ticket:9948

    Workaround for #9948. Warn devs to delete component CSS file along with theme generated file in one run to avoid webpack compilation errors and application restart.

  • ⧉ Extend and clarify valid tag names (#10801). PR:10804. Ticket:9669

  • ⧉ Avoid ConcurrentModificationException in Binder (#10793). PR:10797. Ticket:9217

  • ⧉ Don't update bean property which is read-only bound (#10768). PR:10782. Ticket:9446

  • ⧉ Check assets for url handling (#10746). PR:10756. Ticket:10426

    If a resource is not found in themes folder check also any assets that are copied for the theme.

  • ⧉ Improve locationPrefix impl. PR:10719. Ticket:4730

  • ⧉ Report the parameter name in the exception message. PR:10716. Ticket:9994

  • ⧉ Properly remove block comments from templates (#10701). PR:10713. Ticket:10673

• ⧉ All changes