Repository navigation
Vaadin Flow Components V25.2.0-alpha7
Pre-releaseVaadin Flow Components 25.2.0-alpha7
This is a release of the Java integration for Vaadin Components to be used from the Java server side with Vaadin Flow.
Changes in Flow Components from 25.2.0-alpha6
Changes in All Components
- Chore:
- ⧉ Increase Web-Component version
Changes in vaadin-accordion-flow
- Breaking Changes:
-
⧉ Prevent initial OpenedChangeEvent, set isFromClient correctly. PR:9267. Ticket:2301
Accordionhad two issues with itsOpenedChangeEvent: 1. The event fired on initial attach, even though no user interaction occurred. 2.isFromClient()always returnedtrue, including for server-side changes. Both broke listeners that branch onisFromClient().java Accordion accordion = new Accordion(); accordion.add("1", new Span("Panel 1")); accordion.addOpenedChangeListener(e -> { if (e.isFromClient()) Notification.show("Client opened accordion panel"); });The PR replaces the@DomEvent("opened-changed")listener with a property change listener that fires theOpenedChangeEventwith the correctisFromClient()value, and initializes theopenedproperty properly to prevent the unwanted initial event. 🤖 Generated with Claude Code ---------
-
Changes in vaadin-ai-components-flow
-
New Features:
-
⧉ Add FormAIController field hints API. PR:9290
## Summary - Lets callers attach per-field hints (
describe,allowedValues,ignore) so the LLM gets business semantics that aren't implied by the field's label or type. - Hints are keyed by an opaque id attached to the field component, so they survive removing and re-adding the field within a session. Closes https://github.com/orgs/vaadin/projects/103/views/3?pane=issue&itemId=186540736 🤖 Generated with Claude Code -
⧉ Add FormAIController skeleton. PR:9287
## Summary - Adds the discovery slice of
FormAIController: walks anyHasComponentscontainer, recursively, and stamps each discoveredHasValuewith an opaque UUID id stored on the field component viaComponentUtil.setData. - Ids are plainStrings — no wrapper class, no per-controller cache. The id survives removing and re-adding a field within a session, and future hint state can key off it. - No tools yet —getTools()returns an empty list. The LLM-facing surface lands in follow-up PRs. Closes https://github.com/orgs/vaadin/projects/103/views/3?pane=issue&itemId=186538897 🤖 Generated with Claude Code --------- -
⧉ Add response failed and request start hooks to ai controller. PR:9274
## Description This PR: - Adds the following to
AIController: -void onRequestStart(): Fires synchronously on the UI thread before the LLM stream opens. Throwing aborts the turn and routes toonResponseFailed. Default does nothing. -void onResponseFailed(Throwable): Fires on stream error, timeout, or any pre-stream throw. Mutually exclusive withonResponseComplete, every turn fires exactly one of the two. Default does nothing. - UpdatesAIOrchestratorto uses the new API. Exceptions thrown from either hook are caught and logged; Errors propagate. Fixes https://github.com/orgs/vaadin/projects/103/views/1?filterQuery=&pane=issue&itemId=186537285 ## Type of change - [ ] Bugfix - [x] Feature ## Checklist - [x] I have read the contribution guide: https://vaadin.com/docs/latest/contributing/overview - [x] I have added a description following the guideline. - [x] The issue is created in the corresponding repository and I have referenced it. - [x] I have added tests to ensure my change is effective and works as intended. - [x] New and existing tests are passing locally with my change. - [x] I have performed self-review and corrected misspellings. - [x] Enhancement / new feature was discussed in a corresponding GitHub issue and Acceptance Criteria were created.
-
-
Fixes:
-
⧉ Discard pending states on failed request. PR:9282
## Description This PR updates the
GridAIControllerandChartAIControllerto use theAIControllerhooksonRequestStartandonResponseFailedin order to discard pending states on failed requests. No related issue. Follow-up to #9274. ## Type of change - [x] Bugfix - [ ] Feature ## Checklist - [x] I have read the contribution guide: https://vaadin.com/docs/latest/contributing/overview - [x] I have added a description following the guideline. - [x] The issue is created in the corresponding repository and I have referenced it. - [x] I have added tests to ensure my change is effective and works as intended. - [x] New and existing tests are passing locally with my change. - [x] I have performed self-review and corrected misspellings.
-
Changes in vaadin-checkbox-flow
- Breaking Changes:
Changes in vaadin-dashboard-flow
- New Features:
-
⧉ Add row height API to Dashboard. PR:9219
## Summary - Adds
setRowHeight(String)/getRowHeight()toDashboard, mapping to the--vaadin-dashboard-row-heightCSS custom property introduced in the underlying web component. - When set, the fixed row height overrides the minimum row height and prevents rows from growing to fit their content, allowing widgets to use100%height for their inner content. Closes vaadin/web-components#10943 Depends on vaadin/web-components#11603 🤖 Generated with Claude Code
-
Changes in vaadin-map-flow
- Fixes:
-
⧉ Restore NpmPackage annotation with ol dep, downgrade ol dep to 10.6.0. PR:9256
Reverts #9254
-
⧉ Remove explicit ol
@NpmPackage, let @vaadin/map own it. PR:9254Removing the explicit
ol@NpmPackagedeclaration that conflicted with the version declared by@vaadin/mapitself.@vaadin/map@25.2.0-alpha10already declaresol: "10.6.0"as a direct dependency. Declaringol: "10.6.1"here created a version conflict that was silently masked by pnpm--shamefully-hoist=true, but broke with the switch tonode-linker=hoistedin vaadin/flow: Vite ended up bundling two separate OpenLayers instances, causingsynchronize()to operate on a differentMapobject than the one exposed viamapElement.configuration. Related to vaadin/flow#24307
-
Compatibility
- This release use Web Components listed in Vaadin Platform 25.2.0-alpha7
- Tested with Vaadin Flow version 25.2.0-alpha12