vaadin/flow 24.4.0.beta3

Vaadin Flow 24.4.0.beta3

on GitHub

Changes since 24.4.0.beta2

All changes

Breaking changes

• Rename createWebComponent method (#19309)
  Commit · Pull request

  Rename the createWebComponent function as the create gives the impression that the function is heavy.

Fixes

• Provide specific package-lock.json for hybrid applications (#19342)
  Commit · Pull request · Issue

  The package-lock.json provided by the pre-compiled dev-bundle contains no Hilla dependencies, slowing down the first frontend build. This change attempts to extract a package-lock.json file specific to the hybrid application from the bundle, possibly falling back on the standard one.

• Set page title to documentTitleSignal (#19329)
  Commit · Pull request · Issue

  UIInternals#setTitle(String) sets page title via JavaScript to document.title and optionally window.Vaadin.documentTitleSignal.value where documentTitleSignal is expected but not limited to be Signal type with a value field. This allows Hilla main layout, when used, being kept in sync with the Flow page title even when set via PageTitle annotation or HasDynamicTitle interface.

• Change type of Menu order to double (#19332)
  Commit · Pull request · Issue

  Changing Menu#order type double and MenuData#order type to Double to match it with Hilla's ViewConfig type number.

• Reload flow after hmr reload in dev mode (#19323)
  Commit · Pull request · Issue

  Reset and reload flow when a template hrm reload happens.

• Fix failure when Vite sends many messages in sequence (#19340)
  Commit · Pull request

  Sending multiple messages at the same time resulted in java.lang.IllegalStateException: The remote endpoint was in state [TEXT_FULL_WRITING] which is an invalid state for called method which originates in calling browserSession.getAsyncRemote().sendText a second time before the complete callback for the first call has been called. Now the getBasicRemote() method is used instead which blocks until the message has been sent.