vaadin/flow 7.0.0.alpha1

Vaadin Flow 7.0.0.alpha1

on GitHub

Vaadin Flow 7.0.0.alpha1

Changes in Flow from 6.0.0.beta1

• Breaking Changes:

  • ⧉ Mark AbstractSinglePropertyField class as abstract. PR:9872

  • CSS files matching the pattern *.global.css can NOT be imported into a variable in a TypeScript view. This is a limitation related to the global CSS loader feature mentioned below, but this has already been reverted and will not be a limitation in the next pre-release anymore.

• New Features:

  • ⧉ Use superclass of VaadinServlet/Request if possible. PR:9699

    Makes it possible to use another VaadinService implementations than the built-in VaadinServletService.

  • ⧉ Process Iterable same way as Collection type. PR:9709. Ticket:9256

    The endpoint generator testing setup requires a separate package for each test to avoid interference between tests. This is because the generator in the tests emits all classes per package.

  • ⧉ Add getters for used Unit to HasSize. PR:9824

    Related to #8533 (comment)

  • ⧉ Global CSS loader. PR:10036

    Closes #9970.
    This feature has since been reverted and won't be included in the next release so you can safely ignore this feature. We recommend using a custom theme for loading global styles instead.

  • ⧉ Enable fetching browser URL. PR:10024

    Page::fetchCurrentUrl can be used to asynchronously get the current url from the browser. Closes #1897

• Fixes:

  • ⧉ Execute error handling as a last action in message handler. PR:10142. Tickets:9647, 9705

  • ⧉ Set default PWA start_url as "." instead of "". PR:10194. Tickets:10148.
    Fix a bug that a PWA cannot be installed.

  • ⧉ Offline path should be relative to current path not root. PR:10191
    Fix a bug that cannot offline start a custom offline page with non-root context path.

  • ⧉ Don't clean registry on every new routes set. PR:10162. Ticket:10109

    RouteRegsitry should not be cleaned up every time when new routes are set: there may be interim registry modification which adds routes. Such routes should not be removed but they should stay in the registry.

  • ⧉ Do not emit errors for unused variables/imports/parameters. PR:10150. Ticket:10147

  • ⧉ Treat "clear all" as permanent initial state. PR:10128. Ticket:10119

  • ⧉ Service worker communicate offline state to client. PR:10007

  • ⧉ Remember original state after LOADING. PR:10099

    Added method loadingFailed transitioning to CONNECTION_LOST if it is the last active loading. Also removed the exposed Vaadin.Flow.clients.TypeScript.loadingStarted / loadingFinished pair, as blocking TB is anyway not working for multiple ongoing backend calls (and it would be better handled by register ConnectionState as a Flow client with isActive flag).

  • ⧉ Add style-loader dependency. PR:10085

  • ⧉ Update stylesheet polyfill. PR:10025. Ticket:9869

  • ⧉ 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

  • ⧉ Check if Flow is initiated for connectin indicator. PR:10046

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

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

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

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

  • ⧉ Level up namespace of devModeGizmo and theming objects to Vaadin. PR:10014. Tickets:9905
    TestBench wait logic is based the existence of Flow object and in Fusion Only apps Flow object should not be initialized. moving _vaadintheme_something and devModeGizmo to Vaadin namespace

  • ⧉ Use latest webpack 4 to fix using npm v7. PR:10012. Ticket:10011

  • ⧉ Ensure app shell is always in offline manifest. PR:9979. Ticket:9977