Releases: vaadin/flow
Vaadin Flow 24.5.0.alpha15
Changes since 24.5.0.alpha14
Fixes
-
Options should correct the reactEnable flag
Commit · Pull requestThe reactEnable flag should be automatically corrected to false if vaadin router is used instead of react router.
-
Clean outlet automatically
Commit · Pull requestRemove outlet for layout element automatically so that we don't end up with multiple outlets on the page.
-
React file not added when reactEnabled false
Commit · Pull request · IssueDo not add the outlet file if react is not enabled as the required react node files are not available.
-
Validate Layout annotation
Commit · Pull requestAdd validation that Layout annotated classes are on classes that extend RouterLayout.
Vaadin Flow 24.5.0.alpha14
Changes since 24.5.0.alpha13
Fixes
-
Use 8080 as the default launch port for opening the browser
Commit · Pull request · Issue -
Make outlet a jar file instead of generated
Commit · Pull request
Vaadin Flow 24.5.0.alpha13
Changes since 24.5.0.alpha12
New features
-
Create Fieldset - Legend Java API
Commit · Pull request · IssueJava API to create a and html tag without using a custom Java class to group fields.
Fixes
-
Add react classes in optimized mode
Commit · Pull requestAdd the react classes as found for optimized bundle.
Vaadin Flow 24.5.0.alpha12
Vaadin Flow 24.5.0.alpha11
Changes since 24.5.0.alpha10
New features
-
Automatic Flow layout
Commit · Pull requestAutomatically match layout for both flow and hilla route. format Add server layout usage information to routes.tsx template This reverts commit bad2fec. Have OutletElement as a tsx file in flow-react jar Add javadoc for auto layout getParentLayout method
-
Binder record support
Commit · Pull request
Fixes
-
Block new users immediately when enforcement=ON
Commit · Pull request -
Use Thread context ClassLoader for loading I18n ResourceBundle
Commit · Pull request · IssueResourceBundle caches resources internally, this affects translation resources for the I18n feature. However, after a hot reload of a SpringBoot application in dev mode, up-to-date translations are expected in the output. With this change, a RestartClassLoader is used in SpringBoot applications for loading translation ResourceBundle, so that the translation bundles are reloaded on hot reload.
-
Downgrade to glob 10.4.5 which is Node 18 compatible
Commit · Pull request -
Preserve record prop order, sort for beans
Commit · Pull requestUntil now, bean properties have not been ordered by Flow. Instead they have been ordered by components using the property set, e.g. Grid. Now that we support records, we'd like to maintain original definition ordering for record props, but do sorting for bean props (since for beans you can't get the definition order). This PR makes BeanPropertySet differentiate the two cases and return an ordered stream of properties for beans only.
-
HierarchicalDataCommunicator doesn't support estimates
Commit · Pull request · Issue
Vaadin Flow 24.5.0.alpha10
Changes since 24.5.0.alpha9
New features
-
Strongly cache Copilot files
Commit · Pull requestSpeeds up every reload as there is no need to check if the files have changed
Fixes
-
Use URLClassLoader with ResourceProvider in Maven plugins
Commit · Pull request · IssueResourceProvider ignored the actual project's resources when using the default ClassLoader. This resulted in loading
vaadin-featureflags.properties
from the vaadin-dev-bundle jar, even though there is a file in the project.
Vaadin Flow 24.5.0.alpha9
Changes since 24.5.0.alpha8
New features
-
Add support for Daily Active User feature
Commit · Pull requestIntegrates with License Checker to add support for Daily Active User feature for DAU enabled production build artifacts.
-
Push and replace without navigation callback
Commit · Pull request · IssueAdd feature to support replace and push without getting a callback to the server for the change.
-
Add CompletableFuture WebStorage API
Commit · Pull request · IssueAdds CompletableFuture methods for WebStorage.getItem.
Fixes
-
Fix hierarchical keys passivation
Commit · Pull request -
Rename lock file
Commit · Pull requestRename the flow-node-tasks lock file to vaadin-node-tasks so it doesn't confuse application state when running a non flow build. Closes #19187
-
Always generate routes.tsx
Commit · Pull request · IssueAlways generate the routes.tsx into frontend/generated. Even when routes.tsx is defined in frontend by the developer so that it can be used as an example.
-
Apply CssImport to exported webcomponent
Commit · Pull request · IssueCssImport annotation with just a value attribute can be injected automatically to shadow root of all exported web components (embedded applications) using Constructable StyleSheets. WebComponentExporter should have a theme to make automation work properly in theme-generator.js. Theme property "autoInjectGlobalCssImports": true in theme.json enable auto injection. Disabled by default.
-
Unify client route to match server route format
Commit · Pull request · IssueMake the client route string on the error page in dev mode not start with / so it is the same as for server-side routes.
-
Do not block navigation to current url
Commit · Pull request · IssueLets navigation cause server round-trip, when navigation is triggered by clicking a link.
Vaadin Flow 24.4.6
Changes since 24.4.5
New features
-
Push and replace without navigation callback (#19736)
Commit · Pull request · IssueAdd feature to support replace and push without getting a callback to the server for the change.
Fixes
-
Rename lock file (#19751)
Commit · Pull requestRename the flow-node-tasks lock file to vaadin-node-tasks so it doesn't confuse application state when running a non flow build. Closes #19187
-
Always generate routes.tsx (#19749)
Commit · Pull request · IssueAlways generate the routes.tsx into frontend/generated. Even when routes.tsx is defined in frontend by the developer so that it can be used as an example.
-
Unify client route to match server route format (#19742)
Commit · Pull request · Issue -
Apply CssImport to exported webcomponent (#19740)
Commit · Pull request · IssueCssImport annotation with just a value attribute can be injected automatically to shadow root of all exported web components (embedded applications) using Constructable StyleSheets. WebComponentExporter should have a theme to make automation work properly in theme-generator.js. Theme property "autoInjectGlobalCssImports": true in theme.json enable auto injection. Disabled by default.
-
Do not block navigation to current url (#19730)
Commit · Pull request · IssueLets navigation cause server round-trip, when navigation is triggered by clicking a link.
Vaadin Flow 23.5.3
Changes since 23.5.2
Fixes
-
Apply CssImport to exported webcomponent (#19740) (CP: 23.5)
Commit · Pull request · IssueCssImport annotation with just a value attribute can be injected automatically to shadow root of all exported web components (embedded applications) using Constructable StyleSheets. WebComponentExporter should have a theme to make automation work properly in theme-generator.js. Theme property "autoInjectGlobalCssImports": true in theme.json enable auto injection. Disabled by default.
Vaadin Flow 24.3.15
Changes since 24.3.14
Fixes
-
Apply CssImport to exported webcomponent (#19740)
Commit · Pull request · IssueCssImport annotation with just a value attribute can be injected automatically to shadow root of all exported web components (embedded applications) using Constructable StyleSheets. WebComponentExporter should have a theme to make automation work properly in theme-generator.js. Theme property "autoInjectGlobalCssImports": true in theme.json enable auto injection. Disabled by default.