vaadin/flow 6.0.0.beta4

Vaadin Flow 6.0.0.beta4

on GitHub

Vaadin Flow 6.0.0.beta4

Changes in Flow from 6.0.0.beta3

• New Features:

  • ⧉ Global CSS loader (#10036). PR:10060

    This makes it so that you can import a CSS file into document scope with an import like:

    import './about-view.global.css';

    (using a *.global.css filename suffix)
    instead of needing something like:

    import '!style-loader!css-loader!./about-view.css';

• Breaking Changes and Deprecations:

  • CSS files matching the pattern *.global.css can NOT be imported into a variable in a TypeScript view.

    If you happen to be using CSS filenames that match *.global.css and importing them into TypeScript views with syntax like:

    import styles from './my-component.global.css';

    and expecting that styles would be a CssResult or a string containing the styles, this will break due to new feature that handles loading of *.global.css files differently. See "Global CSS loader" above under New Features.

  • Importing CSS files into TypeScript is deprecated in cases when the CSS filename doesn't match *.shadow.css.

    For example when you want to import a CSS file into a variable in a LitElement component for usage in static get styles() getter (so that the styles are injected into the shadow root of the component) the CSS filename should match *.shadow.css to be forwards compatible. The behaviour will likely be changed in the next major version so that *.shadow.css is required to do this, and all other CSS imports will instead get injected into the document (like the new *.global.css import behaviour does now).

    You should be using the filename suffix *.shadow.css from now on when you need to use this import syntax in TypeScript:

    import styles from './my-component.shadow.css';

    This makes it clear that these styles are meant to be used in a shadow root. In new projects starting from this version (or later) you should see a deprecation highlight in usages of styles (depending on your IDE) in this case if the import filename doesn't match *.shadow.css. If you already have a types.d.ts file in your project you need to delete the file and run the application so that the file is automatically regenerated to include information about the new deprecation and make it visible in your IDE.

• Fixes:

  • ⧉ Remove obsolete client engine pre-compression. PR:10022

    Since 15 all goes through webpack tooling and gets compressed there. Also fixes build on arm based macs, due the issues with abandoned jbrotly project

  • ⧉ Make FCR try to attach child on appear (#9783). PR:10053. Ticket:/vaadin/flow-components#437

    This change is to workaround a buggy behavior related with flow-component-renderer and iron-list.

  • ⧉ Check if Flow is initiated for connectin indicator (#10046). PR:10047

    It fixes a bug when the connection indicator is shown incorrectly.

  • ⧉ NumberValidator accepts undefined for optional fields. PR:10026

    It fixes a bug that user cannot save a new entity in a TypeScript form.

  • ⧉ Resolve requested range properly after filtering the lazy backend (#10020). PR:10027. Ticket:9988

  • ⧉ Level up namespace of devModeGizmo and theming objects to Vaadin (#10014). PR:10016. Tickets:9905

    Fixes testing for apps with only Fusion views. TestBench wait logic is based the existence of Flow object and in Fusion Only apps Flow object should not be initialized. Moved _vaadintheme_something and devModeGizmo to Vaadin namespace