github vaadin/flow 25.1.0-rc1
Vaadin Flow 25.1.0-rc1

pre-release9 hours ago

Changes since 25.1.0-beta3

All changes

New features

  • BuildFrontend Incremental build (#23884)
    Commit · Pull request

    Add incremental build to the buildFrontend task. Closes #17354

  • Retain local signal values during hotswap (#23854)
    Commit · Pull request · Issue

    Automatically transfer local signal values from old view fields to matching fields in the new view during hotswap refresh.

  • Add local web components plugin to vite.generated.ts (#23793)
    Commit · Pull request

    Auto-detects a web-components/node_modules directory in the project root and redirects @polymer/* and @vaadin/* imports to it in dev mode. A custom folder can be specified through vite.config.ts using the overrideVaadinConfig mechanism.

Fixes

  • Use targeted item refresh when signal-bound item value changes (#23913)
    Commit · Pull request · Issue

    • Add a two-argument refreshItem(T newItem, T oldItem) overload to DataProvider, DataView, and related classes, enabling targeted refresh when an item's identity changes (e.g., signal-bound items replaced with new instances) - DataRefreshEvent now carries an optional old item reference via getOldItem(), allowingDataCommunicator and KeyMapper to remap from the old identity to the new one instead of failing to find the item - HierarchicalDataCommunicator throws UnsupportedOperationException for identity-changing refreshes, deferring TreeGrid bindItems support to a future change
  • Move thread start out of DevServerWatchDog constructor (#23898)
    Commit · Pull request

    Starting a thread in a constructor can expose a partially constructed object. Extract the thread start into a separate start() method that callers invoke after construction completes.

  • Use String type for Style.bind return value (#23888)
    Commit · Pull request

    Change Style.bind(String, Signal<String>) return type from SignalBinding<?> to SignalBinding<String> since the method always accepts a Signal<String> and we always know the value type is String. This provides better type safety and eliminates the need for casts when using the binding's onChange callbacks.

  • Route with context path name (#23836)
    Commit · Pull request · Issue

    the same start as the context path from clearing context path out from the url when using react router.

Don't miss a new flow release

NewReleases is sending notifications on new releases.