Releases: vaadin/flow
Vaadin Flow 24.8.0.alpha15
No changes since 24.8.0.alpha14
Vaadin Flow 24.8.0.alpha14
Changes since 24.8.0.alpha13
New features
-
Initialize signals environment (#21490)
Commit · Pull request -
Create transfer util (#21478)
Commit · Pull request · IssueCreate a TransferUtil for handling data transfer for upload and download. For upload handle xhr vs multipart part vs multipart iterator. This makes the UploadHanlder interface easier to handle.
-
Make current user available without an AuthenticationContext instance
Commit · Pull requestMakes it possible to write an application method like
public static Optional<User> getCurrentUser() { return AuthenticationContext.getCurrentAuthenticatedUser(AppUserInfo.class).map(AppUserInfo::user); }instead of re-implementing everything from AuthenticationContext -
Add a shortcut to get DeploymentConfiguration from UIInternals
Commit · Pull requestSummary of Change: Added a helper method in UIInternals to get deployment configurations from the service from the session. Motivation and Context: There are many areas of code that need to access deployment configuration from UIInternals but accessing is quite clunky and long.
-
Add overloads with TransferContext
Commit · Pull request
Fixes
-
Set download attribute for Anchor DownloadHandlers (#21512)
Commit · Pull requestPart of #21487 add tests
-
Remove name/fileName from inputStreamDownload
Commit · Pull requestRemove the possibility to give fileName/name to inputStreamDownloadHandler as the atual downloaded name is decided on transfer and will in many cases not match or be confusing to match in 2 places.
-
Handle downloads where the server does not provide content-length
Commit · Pull request
Vaadin Flow 2.12.0.alpha3
No changes since 2.12.0.alpha2
Vaadin Flow 2.12.0.alpha2
Changes since 2.12.0.alpha1
New features
-
Upgrade webpack to version 5 (2.12)
Commit · Pull requestUpdated webpack to version 5 Replaces file-loader with Webpack 5 assets feature, as recommanded in the migration guide Bumps several npm dependencies Update webpack configuration to correctly handle /VAADIN public path both in dev and prod modes. Update flow Javascript plugins to adapt to webpack dependencies changes Part of #21334
Vaadin Flow 24.8.0.alpha13
Changes since 24.8.0.alpha12
Breaking changes
-
Add setter helpers to DownloadEvent and new method for inline
Commit · Pull requestRefactors the DownloadEvent to be a normal class. Removed the getters for file name, type and size and add setters instead that are basically helper methods for setting various attributes to a response. Adds inline method so that you can call DownloadHandler.forFile(new File("path/to/file")).inline() and the download will be inlined onto page.
-
Add setContentLengthLong to VaadinResponse
Commit · Pull requestAdd the setContentLengthLong method to VaadinResponse.
New features
-
Make an Executor available through VaadinService
Commit · Pull requestProvides access to an Executor instance from VaadinService to submit asynchronous tasks. The default single-threaded executor can be replaced by a custom instance by registering it with a VaadinServiceInitListener. The spring add-on tries to detect an existing TaskExecutor bean, otherwise it falls back to the default executor. To provide a specific TaskExecutor bean, different from the application default, the bean definition can be named VaadinTaskExecutor or be annotated with
@VaadinTaskExecutor.
Fixes
-
Do not set Content-Disposition for null file name
Commit · Pull request -
Improve javadoc and handle unknown content length as -1
Commit · Pull requestBetter explains the methods in DownloadEvent, TransferContext, fromInputStream factory methods in download handler as well as explains -1 for unknown length and handles it accordingly.
-
Inline download in data html elements
Commit · Pull requestAutomatically sets pre-defined download handlers to inline in data html components.
-
Call successhandler from access block
Commit · Pull requestRunning successhandler callback from access so that UI can be updated directly based on the received data.
-
Remove faulty method
Commit · Pull requestremove sendUploadResponse as ResponseHandled is used and should be the one to override for custom responses.
-
Rename allowInert for ElementRequestHandler
Commit · Pull requestRename allowInert to isAllowInert
-
Add IOException to handlers signature
Commit · Pull request -
Read PageTitle annotation from application-defined class
Commit · Pull request · IssueIf a route component instance is proxied by a DI frameworks the PageTitle annotation from the concrete class might not be accessible because it is not inheritable. This change tries to read the annotation from the application-defined class instead of using the route instance class directly.
-
Update JavaDocto be more descriptive
Commit · Pull requestUpdate overload JavaDoc to have description of difference in the first sentence.
-
Add error message and update javadoc on DownloadResponse
Commit · Pull requestAdd possibility to give an error message to the DownloadResponse. Add information on stream handling for DownloadResponse so it is clear that the one using the response is responsible for closing stream.
-
Make addTransferProgressListener protected
Commit · Pull requestaddTransferProgressListener is redundant because we already expose shortcut fluent methods and factory methods where the listener is present. if needed, custom handlers extending the abstract class can use this method in constructors or make it public.
-
Do not lock the session while transferring content
Commit · Pull requestFor common cases let's not lock the session for data transfer and assume that this locking can be done in a custom handler, if required.
-
Update read revision before applying changes
Commit · Pull requestThe logic that determines whether a computed signal or effect should be run again is triggered from a change observer. If the value used by that change observer was already captured in the read transaction, then the old value would be used instead of the new one when the value is changed which would mean that the change remains undetected.
-
Check DisabledUpdateMode and isVisible in element request validation
Commit · Pull requestThis takes into account the DisabledUpdateMode parameter of ElementRequestHandler and isVisible property of the owner element when validating the request in StreamRequestHandler.
Vaadin Flow 23.6.0.alpha3
No changes since 23.6.0.alpha2
Vaadin Flow 24.8.0.alpha12
Changes since 24.8.0.alpha11
Breaking changes
- Renamings in new handlers API
Commit · Pull request
New features
-
Introduce VaadinSecurityConfigurer for modular security configuration
Commit · Pull requestIntroduced
VaadinWebSecurityConfigurerto improve modularity and readability, with almost the same logic present inVaadinWebSecurity. This change promotes reusability and better separation of concerns while maintaining existing functionality. -
Add factory method for UploadHandler
Commit · Pull request · IssueAdd factory methods for in-memory, File and TemporaryFile for easier handling of upload.
Code refactoring
- Extract service worker plugin into internal package
Commit · Pull request
Vaadin Flow 24.8.0.alpha11
Changes since 24.8.0.alpha10
New features
-
Add TransferProgressListener API
Commit · Pull requestThis is the first part for DownloadHandler.
-
Add UploadHanlder interface
Commit · Pull requestAdd upload handler callback when xhr upload happens.
Fixes
-
Preserve handler type when chaining listener methods
Commit · Pull requestAllows getting the proper type instead of TransferProgressAwareHandler to pass to component.
-
ElementRequestHandler node state handling
Commit · Pull request · Issue -
Prevent potential errors by checking for module.forHMROnly before assignment
Commit · Pull request -
Prevent file watcher threads from slowing down JVM shutdown
Commit · Pull requestFileWatcher was using an executor that creates non-daemon threads to watch for file changes. This caused a delay in JVM shutdown, as it would wait at least 60 seconds for all threads in the executor pool to be evicted. This change provides a custom thread factory that creates daemon threads for the executor to prevent JVM shutdown delays.
Vaadin Flow 24.7.6
Changes since 24.7.5
Fixes
-
Prevent potential errors by checking for module.forHMROnly before assignment (#21374)
Commit · Pull request -
Prevent file watcher threads from slowing down JVM shutdown (#21365)
Commit · Pull requestFileWatcher was using an executor that creates non-daemon threads to watch for file changes. This caused a delay in JVM shutdown, as it would wait at least 60 seconds for all threads in the executor pool to be evicted. This change provides a custom thread factory that creates daemon threads for the executor to prevent JVM shutdown delays.
Vaadin Flow 24.6.12
Changes since 24.6.11
Fixes
-
Prevent file watcher threads from slowing down JVM shutdown (#21365)
Commit · Pull requestFileWatcher was using an executor that creates non-daemon threads to watch for file changes. This caused a delay in JVM shutdown, as it would wait at least 60 seconds for all threads in the executor pool to be evicted. This change provides a custom thread factory that creates daemon threads for the executor to prevent JVM shutdown delays.