Skip to content

Vaadin Flow Components V25.2.0-alpha8

Pre-release
Pre-release

Choose a tag to compare

@vaadin-bot vaadin-bot released this 21 May 12:27
· 658 commits to main since this release
95e7f3c

Vaadin Flow Components 25.2.0-alpha8

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-alpha7

Changes in All Components

  • Chore:
    • ⧉ Increase Web-Component version

Changes in vaadin-ai-components-flow

  • New Features:
    • ⧉ Add binder integration to form ai controller. PR:9308

      ## Description This PR: - Adds a FormAIController(container, Binder<?>) overload. - Property-named bindings (bind("name"), bindInstanceFields(this), @PropertyId(...)) contribute the bean property name as a default for the field's description — surfaced to the LLM alongside the field's label and helper text. The field's tool-call id stays an opaque UUID assigned at discovery time; the property name is description-side metadata only. - Seeding only fills nulls: an explicit describe(field, "...") always wins. Lambda-bound bindings and unbound fields contribute no default. - Adds a package-private findBinding(field) returning the live binding for any field on the supplied binder, or an empty optional for unbound fields and for controllers constructed without a binder. Fixes https://github.com/orgs/vaadin/projects/103/views/1?filterQuery=&pane=issue&itemId=186542732 ## 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.

    • ⧉ Add get_form_state tool to FormAIController. PR:9307

      ## Summary - The form filler needs the LLM to know which fields exist, what each one means, and what each one currently holds before it can decide what to fill — get_form_state is the controller-side contract that delivers that view as JSON. - Schema rendering handles the awkward edges the LLM would otherwise stumble on: BigInteger without overflow, non-finite doubles as JSON null, BigDecimal in plain (non-scientific) form, multi-select shape via items, per-field error isolation so one bad field doesn't kill the whole payload. - Classification recognises real Vaadin selection components (HasItems, HasDataView, HasLazyDataView, HasListDataView) and the full integer/number value-type families, so ComboBox/Select and custom Long/Short/Float fields all land in the right schema bucket. 🤖 Generated with Claude Code ---------

    • ⧉ Lock form fields during AI fill turn. PR:9298

      ## Summary - Prevent the user from typing into a field the AI is about to overwrite by switching every non-ignored, currently-editable field to read-only for the duration of a fill turn, releasing on success, failure, or timeout. - Document the limitation that application code which toggles a field's read-only state mid-turn (e.g. a value-change listener reacting to the LLM's writes) will be overridden when the controller releases its locks — applications should avoid mid-turn toggling, or reapply state after the turn completes. Related to https://github.com/orgs/vaadin/projects/103/views/3?pane=issue&itemId=186543521 🤖 Generated with Claude Code ---------

    • ⧉ Add value options API to FormAIController. PR:9297

      ## Summary - Add valueOptions(...) on FormAIController so callers can declare which values the LLM may pick — either via a query callback or a fixed list of labels — together with a toValue converter that turns the chosen label back into the field's value type. - Expose a query_field_options LLM tool so the model fetches labels lazily by filter/limit, which keeps large or dynamic option sets out of the prompt and lets developers back fields with arbitrary data sources. Related to https://github.com/orgs/vaadin/projects/103/views/3?pane=issue&itemId=186541698 Closes https://github.com/orgs/vaadin/projects/103/views/3?pane=issue&itemId=186556651 🤖 Generated with Claude Code ---------

Changes in vaadin-checkbox-flow

  • Fixes:
    • ⧉ Restore and deprecate CheckboxVariant helper variants. PR:9309

      ## Description Restored variants removed in #9293 and marked as deprecated for removal. Related to mstahv/vaadin-ecosystem-build#131 ## Type of change - Bugfix

Changes in vaadin-combo-box-flow

  • New Features:
    • ⧉ Add setFocusSelectedItem to ComboBox. PR:9239

      Restores the pre-vaadin/web-components#6055 behavior of focusing the currently selected item when the combo-box dropdown opens, behind an opt-in flag. java comboBox.setFocusSelectedItem(true); For lazy data providers, an ItemIndexProvider must be configured so the selected item's index can be resolved against the current sorting; otherwise opening the dropdown throws UnsupportedOperationException. In-memory data works out of the box. Part of vaadin/web-components#6061 --- 🤖 Generated with Claude Code ---------

Changes in vaadin-grid-flow

  • Fixes:
    • ⧉ No ItemClickListener for component with overlay. PR:9292. Ticket:9288

      Do not fire ItemClickEvent if the click originated inside a Vaadin overlay of a component inside a Grid cell. Closes vaadin/flow#17821

Compatibility