Skip to content

Vaadin Flow 23.2.5
Compare
Choose a tag to compare
@vaadin-bot vaadin-bot released this 24 Oct 06:27
· 85 commits to 23.2 since this release
23.2.5
22f053b
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Changes since 23.2.4

All changes

Fixes

  • Use access and not lock (#14827)
    Commit · Pull request · Issue

    Use access so that we do not deadlock.

  • AbstractDataProvider serialization (#14870)
    Commit · Pull request · Issue

    Replace lambda with anonymous inner class in AbstractDataProvider to fix serialization issue(s). Test available in flow-components project since the issue only happens when the data provider is used with a grid.

  • Synchronize pwa handler on map (#14838)
    Commit · Pull request

    Synchronize pwa handler on the requestHandlerMap instead of locking the session. Locking and unlocking session may fire a push event that might make the server client sync faulty. touches #14797

  • Old node installation (#14840)
    Commit · Pull request · Issue

    node installation we check the correc path for npm script.

  • Locking on FeatureFlags instead of VaadinContext (#13962) (#14741)
    Commit · Pull request · Issue

    Only lock on FeatureFlags when checking for wrapper and initializing

  • Linux node installation (#14657)
    Commit · Pull request · Issue

    NodeJS 18 is more strict about where the contents are located than old versions.

  • Defer location and query tracking (#14742)
    Commit · Pull request · Issue

    Track of location and query string after response from server happens too early when handling server side navigation, because history.pushState is executed within a setTimeout. This change defers the tracking to the next event loop cycle in order to get the correct values.

  • Redirect if refresh token is in push response also (#14777)
    Commit · Pull request · Issue

Assets 2