Vaadin Flow Components V23.3.0.rc1

Vaadin Flow Components 23.3.0.beta3

This is a release of the Java integration for Vaadin Components to be used from the Java server side with Vaadin Flow.

Changes in Flow Components from 23.3.0.beta2

Changes in All Components

• Chore:
  • ⧉ Increase Web-Component version

Changes in vaadin-date-picker-flow

• Fixes:

  • ⧉ Restore backward compatibility of new event classes. PR:4290

    When sub-classing components, and using an implicit import for events such as SplitterDragendEvent, then the event classes introduced as an alternative to the deprecated events in generated classes can cause compilation errors. The problem is that the newly introduced event class now shadows the deprecated class, and the new class does not have the generic type param of the deprecated class. Fixed this by adding a generic type param to the new event classes as well. The param will be dropped in v24, which will require developers to update their code during migration accordingly. The breaking change should be mentioned in the release notes, and in the migration guide.

Changes in vaadin-dialog-flow

• Fixes:

  • ⧉ Restore backward compatibility of new event classes. PR:4290

    When sub-classing components, and using an implicit import for events such as SplitterDragendEvent, then the event classes introduced as an alternative to the deprecated events in generated classes can cause compilation errors. The problem is that the newly introduced event class now shadows the deprecated class, and the new class does not have the generic type param of the deprecated class. Fixed this by adding a generic type param to the new event classes as well. The param will be dropped in v24, which will require developers to update their code during migration accordingly. The breaking change should be mentioned in the release notes, and in the migration guide.

Changes in vaadin-grid-pro-flow

• Fixes:
  • ⧉ Add null check for item (#4220). PR:4297

Changes in vaadin-notification-flow

• Fixes:

  • ⧉ Restore backward compatibility of new event classes. PR:4290

    When sub-classing components, and using an implicit import for events such as SplitterDragendEvent, then the event classes introduced as an alternative to the deprecated events in generated classes can cause compilation errors. The problem is that the newly introduced event class now shadows the deprecated class, and the new class does not have the generic type param of the deprecated class. Fixed this by adding a generic type param to the new event classes as well. The param will be dropped in v24, which will require developers to update their code during migration accordingly. The breaking change should be mentioned in the release notes, and in the migration guide.

Changes in vaadin-split-layout-flow

• Fixes:

  • ⧉ Restore backward compatibility of new event classes. PR:4290

    When sub-classing components, and using an implicit import for events such as SplitterDragendEvent, then the event classes introduced as an alternative to the deprecated events in generated classes can cause compilation errors. The problem is that the newly introduced event class now shadows the deprecated class, and the new class does not have the generic type param of the deprecated class. Fixed this by adding a generic type param to the new event classes as well. The param will be dropped in v24, which will require developers to update their code during migration accordingly. The breaking change should be mentioned in the release notes, and in the migration guide.

Changes in vaadin-time-picker-flow

• Fixes:

  • ⧉ Restore backward compatibility of new event classes. PR:4290

    When sub-classing components, and using an implicit import for events such as SplitterDragendEvent, then the event classes introduced as an alternative to the deprecated events in generated classes can cause compilation errors. The problem is that the newly introduced event class now shadows the deprecated class, and the new class does not have the generic type param of the deprecated class. Fixed this by adding a generic type param to the new event classes as well. The param will be dropped in v24, which will require developers to update their code during migration accordingly. The breaking change should be mentioned in the release notes, and in the migration guide.

Compatibility

• This release use Web Components listed in Vaadin Platform 23.3.0.beta3
• Tested with Vaadin Flow version 24.0.0.alpha9