Vaadin Flow 24.5.0.alpha17

Changes since 24.5.0.alpha16

All changes

Fixes

• Prevent Flow navigation for Hilla route
  Commit · Pull request

  ---

• No react module for Vaadin Router
  Commit · Pull request · Issue

  Remove reactOutlet module if we are not running react, but are using Vaadin Router inferred from index.ts

• Safely handle nested removal of menu routes
  Commit · Pull request

  MenuRegistry.filterClientViews removes inaccessible routes and their child routes. When iterating the list of all routes, a NPE can occur if a child route has already been removed together with its parent route. Add a check that prevents NPE for removed children.

• Validate layout values
  Commit · Pull request · Issue

  Check Layout annotations for duplicate values. If found throw exception.

• Prevent NPE when creating init parameters
  Commit · Pull request · Issue

  ServletConfig might contain init parameter with null values. This is however not supported by java Properties class. This change adds a null check and logs offending keys for debugging purpose.

Vaadin Flow 24.3.16

Changes since 24.3.15

All changes

Fixes

• Prevent NPE when creating init parameters (#19856) (CP: 24.3)
  Commit · Pull request · Issue

Vaadin Flow 24.5.0.alpha16

Changes since 24.5.0.alpha15

All changes

Fixes

• Options should correct the reactEnable flag
  Commit · Pull request

  The reactEnable flag should be automatically corrected to false if vaadin router is used instead of react router.

Vaadin Flow 24.4.7

Changes since 24.4.6

All changes

Fixes

• Prevent NPE when creating init parameters (#19856)
  Commit · Pull request · Issue

  ServletConfig might contain init parameter with null values. This is however not supported by java Properties class. This change adds a null check and logs offending keys for debugging purpose.

• Use 8080 as the default launch port for opening the browser (#19833)
  Commit · Pull request · Issue

• Use Thread context ClassLoader for loading I18n ResourceBundle (#19791)
  Commit · Pull request · Issue

  ResourceBundle caches resources internally, this affects translation resources for the I18n feature. However, after a hot reload of a SpringBoot application in dev mode, up-to-date translations are expected in the output. With this change, a RestartClassLoader is used in SpringBoot applications for loading translation ResourceBundle, so that the translation bundles are reloaded on hot reload.

• Use URLClassLoader with ResourceProvider in Maven plugins (#19781)
  Commit · Pull request · Issue

  ResourceProvider ignored the actual project's resources when using the default ClassLoader. This resulted in loading vaadin-featureflags.properties from the vaadin-dev-bundle jar, even though there is a file in the project.

Vaadin Flow 24.5.0.alpha15

Changes since 24.5.0.alpha14

All changes

Fixes

• Options should correct the reactEnable flag
  Commit · Pull request

  The reactEnable flag should be automatically corrected to false if vaadin router is used instead of react router.

• Clean outlet automatically
  Commit · Pull request

  Remove outlet for layout element automatically so that we don't end up with multiple outlets on the page.

• React file not added when reactEnabled false
  Commit · Pull request · Issue

  Do not add the outlet file if react is not enabled as the required react node files are not available.

• Validate Layout annotation
  Commit · Pull request

  Add validation that Layout annotated classes are on classes that extend RouterLayout.

Vaadin Flow 24.5.0.alpha14

Changes since 24.5.0.alpha13

All changes

Fixes

• Use 8080 as the default launch port for opening the browser
  Commit · Pull request · Issue

• Make outlet a jar file instead of generated
  Commit · Pull request

Vaadin Flow 24.5.0.alpha13

Changes since 24.5.0.alpha12

All changes

New features

• Create Fieldset - Legend Java API
  Commit · Pull request · Issue

  Java API to create a and html tag without using a custom Java class to group fields.

Fixes

• Add react classes in optimized mode
  Commit · Pull request

  Add the react classes as found for optimized bundle.

Vaadin Flow 24.5.0.alpha12

Changes since 24.5.0.alpha11

All changes

Fixes

• Make outlet tsx generated
  Commit · Pull request

Vaadin Flow 24.5.0.alpha11

Changes since 24.5.0.alpha10

All changes

New features

• Automatic Flow layout
  Commit · Pull request

  Automatically match layout for both flow and hilla route. format Add server layout usage information to routes.tsx template This reverts commit bad2fec. Have OutletElement as a tsx file in flow-react jar Add javadoc for auto layout getParentLayout method

• Binder record support
  Commit · Pull request

Fixes

• Block new users immediately when enforcement=ON
  Commit · Pull request

• Use Thread context ClassLoader for loading I18n ResourceBundle
  Commit · Pull request · Issue

  ResourceBundle caches resources internally, this affects translation resources for the I18n feature. However, after a hot reload of a SpringBoot application in dev mode, up-to-date translations are expected in the output. With this change, a RestartClassLoader is used in SpringBoot applications for loading translation ResourceBundle, so that the translation bundles are reloaded on hot reload.

• Downgrade to glob 10.4.5 which is Node 18 compatible
  Commit · Pull request

• Preserve record prop order, sort for beans
  Commit · Pull request

  Until now, bean properties have not been ordered by Flow. Instead they have been ordered by components using the property set, e.g. Grid. Now that we support records, we'd like to maintain original definition ordering for record props, but do sorting for bean props (since for beans you can't get the definition order). This PR makes BeanPropertySet differentiate the two cases and return an ordered stream of properties for beans only.

• HierarchicalDataCommunicator doesn't support estimates
  Commit · Pull request · Issue

Vaadin Flow 24.5.0.alpha10

Changes since 24.5.0.alpha9

All changes

New features

• Strongly cache Copilot files
  Commit · Pull request

  Speeds up every reload as there is no need to check if the files have changed

Fixes

• Use URLClassLoader with ResourceProvider in Maven plugins
  Commit · Pull request · Issue

  ResourceProvider ignored the actual project's resources when using the default ClassLoader. This resulted in loading vaadin-featureflags.properties from the vaadin-dev-bundle jar, even though there is a file in the project.