vaadin/flow 24.0.0.alpha10

Vaadin Flow 24.0.0.alpha10

on GitHub

Changes since 24.0.0.alpha9

All changes

Breaking changes

• Express Build mode basic support
  Commit · Pull request · Issue

  Express mode is a development time feature where a pre-built bundle is used instead of Vite. The mode is targeted for development where you mostly/only change Java files as there is no on-the-fly compilation of frontend files. Express mode is currently enabled by setting the enableDevServer property to false. This is assumed to change soon. In express mode an application specific bundle is created in the dev-build folder inside the project automatically if the bundle does not exist. This bundle should be committed to the repository so other developers do not have to rebuild it.
  This changes slightly how some features work:

  • Running build-frontend in Maven or Gradle will automatically set the project into production mode. There is no need to separately specify a productionMode parameter for these (any value specified is ignored)

  • If you have earlier run both prepare-frontend and build-frontend in development mode, you should delete the build-frontend execution or move it to a production profile.Instead enable express mode.

• Use dedicated mapping for Vaadin push endpoint
  Commit · Pull request · Issue

  Removes pushUrl configuration option, and instead maps push always to a dedicated path (/VAADIN/push).

New features

• Add a feature flag for Express Build
  Commit · Pull request · Issue

  Adds a feature flag for Express Build and disables dev server forcibly if this feature flag is set.

• Merge JavaScriptBootstrapUI into UI
  Commit · Pull request

• Add the Authentication Context bean to the Vaadin Web Security
  Commit · Pull request · Issue

  • AuthenticationContext is a concrete class that gets access to the authenticated user and allows performing logout integrated with Spring Security - AuthenticationContext is an injectable managed bean - Developers can plug additional LogoutHandlers in VaadinWebSecurity.addLogoutHandlers() - VaadinWebSecurity configures a LogoutSuccessHandler with a redirect strategy that can handle also XHR UIDL requests (UidlRedirectStrategy)

• Add refresh flag to navigation event
  Commit · Pull request · Issue

  Add the isRefreshEvent to BeforeEnterEvent and AfterNavigationEvent to be make it possible to distinguish if the event is for a refresh of a preserve on refresh view.

• Added a shorthand to remove a component from its parent
  Commit · Pull request

  Reduces coupling between UI components (and/or ugly code)

Fixes

• Correctly handle URL encoding in routes
  Commit · Pull request · Issues [10129](https://github.com/vaadin/flow/issues
  /10129), 7454

• Avoid duplicate JS const declaration on license checker script
  Commit · Pull request

  When adding license checker script a global constant name originalCustomElementDefineFn is declared. This produces browser errors in portlet addon, because the script may be added multiple times on the same page. This patch stores the originalCustomElementDefineFn reference under window.Vaadin container and adds a guard to set it only if not already present.

• Added HasDynamicTitle checking in parent layouts
  Commit · Pull request · Issue

  Checks the navigation targets including parent layouts and takes the page title from the one implementing HasDynamicTitle.

• Vite production build errors with transitive dependencies
  Commit · Pull request · Issue

  Modifies the Vite stats.json plugin so that only direct dependencies are considered in npmModules, assuming that transitive dependency versions are not relevant. In addition, includes integration testing setup up with a transitive dependency for Vite, in both development and production modes.

• Do not serve Vite index.html for /index.html
  Commit · Pull request

  In dev mode, the index.html in the project was not used but instead the Vite index.html was served

• Upgrade io.github.classgraph:classgraph from 4.8.149 to 4.8.150
  Commit · Pull request

  Snyk has created this PR to upgrade io.github.classgraph:classgraph from 4.8.149 to 4.8.150. See this package in Maven Repository: https://mvnrepository.com/artifact/io.github.classgraph/classgraph/ See this project in Snyk: https://app.snyk.io/org/artur-x3f/project/2fb5576e-211e-4c52-b560-ff0a6ecea5c2?utm_source=github&utm_medium=referral&page=upgrade-pr

• Npm version collection on windows
  Commit · Pull request

  modules in windows environment.

• Component locale works without UI and i18n
  Commit · Pull request · Issue

  Component locale should return a locale even when UI and i18nProvider are not available.

• Do not remove expanded items from key mapper
  Commit · Pull request · Issue

  With a TreeGrid, the expanded state of a root item gets lost when scrolled enough to request a new range. The cause for this is the updated key of the returned item. The expanded state for the items except the root items do not get lost. This PR makes sure that the key-value pair for a root item persists in the KeyMapper if the item is expanded. This change only affects hierarchical data. A test is added to ensure that the fix solves the issue. While this refactoring is less than ideal in terms of clean code, I think that the alternative requires a much larger refactoring. The logic in the regular and hierarchical data communicators are mostly both coupled and duplicated with private methods at this time. Therefore, this PR is as atomic as possible.

• Use root servlet mapping for push url in OSGi case
  Commit · Pull request

  Fallback to a root mapping for push in case if not servlet registration is available (OSGi runtime).

• Prefix web component client app with wc-
  Commit · Pull request

  Avoids conflicts with the application

• Remove unnecessary clear condition
  Commit · Pull request · Issue

  For hierarchical data, even when the child components are filtered out, the clear method on ArrayUpdater.Update in HierarchicalCommunicationController is never called. This is caused by an if check, in which the start index of previousActive is compared to the newly calculated assumedSize. Since there might be items to clear, the newly calculated size should have no effect on whether we clear the items or not. This check is not present in the DataCommunicator counterpart within the method collectChangesToSend. This PR removes the aforementioned clear condition. Add test to ensure that the expanded children are cleared properly when filtered out.

• Empty alt in costructor should add property
  Commit · Pull request · Issue

  Giving the alternate text in the constructor should generate a property to the image.

• No stream serialization without uis
  Commit · Pull request · Issue

  Do not serialize the streamResourceRegistry if UIs are not serialized.

• Add a template of old tsconfig.json used in OSGi
  Commit · Pull request