Skip to content

Vaadin Flow Components V25.2.0-alpha7

Pre-release
Pre-release

Choose a tag to compare

@vaadin-bot vaadin-bot released this 18 May 11:47
· 672 commits to main since this release
f0092f5

Vaadin 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

      Accordion had two issues with its OpenedChangeEvent: 1. The event fired on initial attach, even though no user interaction occurred. 2. isFromClient() always returned true, including for server-side changes. Both broke listeners that branch on isFromClient(). 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 the OpenedChangeEvent with the correct isFromClient() value, and initializes the opened property 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 any HasComponents container, recursively, and stamps each discovered HasValue with an opaque UUID id stored on the field component via ComponentUtil.setData. - Ids are plain Strings — 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 to onResponseFailed. Default does nothing. - void onResponseFailed(Throwable): Fires on stream error, timeout, or any pre-stream throw. Mutually exclusive with onResponseComplete, every turn fires exactly one of the two. Default does nothing. - Updates AIOrchestrator to 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 GridAIController and ChartAIController to use the AIController hooks onRequestStart and onResponseFailed in 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:
    • ⧉ Remove not working helper-above variants from CheckboxVariant. PR:9293. Ticket:11750

      ## Description The only variant in CheckboxVariant is helper-above-field and it does nothing. Let's remove it as agreed. ## Type of change - Behavior altering change

Changes in vaadin-dashboard-flow

  • New Features:
    • ⧉ Add row height API to Dashboard. PR:9219

      ## Summary - Adds setRowHeight(String) / getRowHeight() to Dashboard, mapping to the --vaadin-dashboard-row-height CSS 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 use 100% 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:9254

      Removing the explicit ol @NpmPackage declaration that conflicted with the version declared by @vaadin/map itself. @vaadin/map@25.2.0-alpha10 already declares ol: "10.6.0" as a direct dependency. Declaring ol: "10.6.1" here created a version conflict that was silently masked by pnpm --shamefully-hoist=true, but broke with the switch to node-linker=hoisted in vaadin/flow: Vite ended up bundling two separate OpenLayers instances, causing synchronize() to operate on a different Map object than the one exposed via mapElement.configuration. Related to vaadin/flow#24307

Compatibility