vaadin/flow 7.0.0.alpha2

Vaadin Flow 7.0.0.alpha2

on GitHub

Vaadin Flow 7.0.0.alpha2

Changes in Flow from 7.0.0.alpha1

• Breaking Changes:

  • ⧉ Remove theme modules from Flow. PR:10220

    As the theme modules are removed from flow-bom and stop following the flow versioning, this is considered a breaking change. Remove the Lumo and Material theme modules from Flow project to have them in the components project instead. Create a test module with Lumo class used for testing in modules requiring the default theme (Lumo). Closes #10182

• New Features:

  • ⧉ Allow spaces in addClassNames arguments array. PR:10354

    Closes #10353

  • ⧉ Add API to control whether Binder converts back to presentation (forward port from FW 8 (#12246))

  • ⧉ Write generated theme file to the generated folder. PR:10262. Ticket:10030

• Fixes:

  • ⧉ Skip InjectManifestPlugin for non PWAs. PR:10361

    It reduces the frontend build time for non-PWAs.

  • ⧉ Make shortcuts not break writing on inputs. Ticket:10362

    Only passes the delegated event forward when it maps to the shortcut key. For the shortcut key, preventDefault() is the default behavior and default can be allowed with allowBrowserDefault() in the ShortcutRegistration.

  • ⧉ Prevent NPE when writing field value to bean. PR:10387

    Forward port vaadin/framework#12230

  • ⧉ Add reflections input filter. PR:10333

    Add input filtering so we only handle class files from the classpath in ReflectionsClassFinder Closes #10304

  • ⧉ Move fusion-endpoint dependency. PR:10334. Ticket:10312

    Move the fusion-endpoint dependency from maven-plugin to plugin-base as it is needed in other plugins also.

  • ⧉ Keep theme generated files from removing by endpoints generator. PR:10316. Ticket:10082

  • ⧉ Fix shortcuts when listenOn is a dialog. PR:10264

    This makes it possible for a component to specify a client side only element that should be used for listening keydown events on when the component is setup as the listenOn target for a Shortcut. This is needed for components like Vaadin Dialog which transport the dialog contents inside an overlay that only exists on the client side and thus breaks shortcut event handling. Related to #7799, vaadin/vaadin-dialog#229
    all changes since previous version