Vaadin Flow 2.6.8
Changes in Flow from 2.6.7
-
Breaking Changes:
-
⧉ Deprecate PageConfigurator since it has broken design (#11521). PR:11530. Ticket:11518
Deprecated due to multiple issues on the feature design, like it won't work together with the
PreserveOnRefresh
annotation. Will not be removed until after the next long term support version. UseBoostrapListener
instead, which provides API for modifying the bootstrap page and access to theUI
, which provides further replacement API likeUI#getLoadingIndicatorConfiguration()
.AppShellConfigurator
is the replacement since Flow 3+ (Vaadin 15+)
-
-
Fixes:
-
fix build issue with npm 7.20.3+ (#11588) (#11591)
Addbabel-loader
to devDependencies to fix issue happening after npm 7.20.3 where the loader gets only installed into a sub node_modules folder and not to root. Closes #11584 -
⧉ Blacklist npm versions (#11585). PR:11587
Add new versions to the NPM blacklist. Update information on that to do about having an blacklisted version. Touches #11584
-
⧉ Don't fire shortcut event if ancestor of component is not visible (#11565). PR:11583. Ticket:7033
-
⧉ Clean up managed default versions (#11563). PR:11568. Ticket:11561
Clean up default dependencies and devDependencies if they have changed.
-
⧉ Only copy javascript files. (#11562). PR:11564
When copygin the webcomponentsjs polyfill do not copy in package.json or the md files. closes #11560
-
⧉ Register data provider listener only if it has not been registered. PR:11550
(cherry picked from commit 067f63f)
-
⧉ Use byte[] instead of String to store stats.json (#11529). PR:11533. Ticket:11515
This is made to avoid excessive memory usage when managing the data.
-
⧉ Set Vaadin session attribute using lock (#11538). PR:11544. Ticket:11519
-
⧉ Reset session field only when HTTP session is invalidated (#11416) (#11492). PR:11499. Ticket:6959
-
⧉ Remove functionality which tries to pin dev dependencies (#11456) (#11477). PR:11483. Ticket:9345
-
⧉ Update mock logging (#11464) (#11474). PR:11475
Update the log check to not use a file as it will most likely bring in problems in concurrent execution
-
⧉ Don't check logger in frontend version validation test (#11463) (#11468). PR:11469
-