Vaadin Flow 7.0.0.beta4
Changes in Flow from 7.0.0.beta3
-
New Features:
-
Fixes:
-
⧉ Use regular string enum instead of a const enum (#10853). PR:10860
Given a Java enum aspubic enum Environment { DEV, TEST, PROD }
Now it is possible to do any object action with the final
Environment
enum on the client-side:Object.keys(Environment).forEach(enumValue => console.log(enumValue));
-
⧉ Remove old router layouts content before navigation (#10973). PR:11007. Ticket:345
Recursively removes content of the all nested router layouts of the given old content when the navigation occurs. This is needed to let Dependency Injection frameworks (Spring and CDI add-ons) to re-create managed components with no duplicates/leftovers.
-
⧉ Change construct-style-sheets-polyfill to be a runtime dependency (#10991). PR:10994. Ticket:10988
-
⧉ Update the used Opcode from 7 to 8 (#10979). PR:10982. Ticket:10870
Update used ClassVisitor ASM version from 7 to 8 to support Java16 record
-
⧉ Use IOUtils toStream and toString (#10975). PR:10976. Ticket:10893
Use IOUtils toString and toInputStream to not change any characters in the file content.
-
⧉ Enable use of external css using
@import
(#10953). PR:10961. Ticket:10228Add fix for using a external css file by having the
@import url(...)
in a css file. Also supports imports with media queries. -
⧉ Use defined version for devDependencies. (#10955). PR:10958
-
⧉ Allow empty segments at start (#10921). PR:10935. Ticket:10729
-
⧉ Pin platform transitive dependencies with npm (#10864). PR:10920. Ticket:10572
Uses the same vaadin_versions.json file based pinning as with pnpm. In case the application has @NpmPackage annotation with a certain version, then that is used over the platform pinned version. When that is older, a warning is logged (like with pnpm). In case a dependency has been pinned directly in package.json, then that is used over the platform pinned version. When that is older, a warning is logged (like with pnpm).
-
⧉ Log limitation of adding new styles while switching themes (#10894). PR:10927. Ticket:10680
If there are more than one theme available in themes folder, user can switch between them in development mode by changing the name of the theme in @theme. As having a watch for adding new styles in component folder is 'static', at least a log about this limitation is needed.
-