Skip to content

Conversation

@vursen
Copy link
Contributor

@vursen vursen commented Jan 19, 2026

Description

Add RangeSlider component that allows selecting a numeric range with two handles. Includes RangeSliderValue record for the start/end value pair and updates SliderBase to support custom value converters.

Depends on

Fixes #8481

Type of change

  • Feature

vursen and others added 4 commits January 19, 2026 19:02
Add RangeSlider component that allows selecting a numeric range with two
handles. Includes RangeSliderValue record for the start/end value pair
and updates SliderBase to support custom value converters.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
Move the "start value cannot be greater than end value" validation from
RangeSlider#setValue to the RangeSliderValue compact constructor, ensuring
the invariant is enforced at construction time.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@vursen vursen changed the title feat: add RangeSlider component with start/end value support feat: create RangeSlider component Jan 26, 2026
vursen and others added 11 commits January 26, 2026 13:44
Add RangeSliderTest with tests for constructors, setValue validation,
interface implementations, and property setters/getters.

Add RangeSliderSerializableTest for serialization testing.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
Add constructors with various parameter combinations including label,
min/max range, step, initial value, and value change listener. Also
add corresponding unit tests for all new constructors.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
Add RangeSliderElement testbench class and basic IT test that verifies
min, max, step, and value properties are correctly set on the component.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
Update RangeSlider to use SerializableBiFunction for value converters,
allowing validation during conversion. Throw exceptions for invalid
min/max/step changes instead of logging warnings. Remove
RangeSliderWarningsTest as warnings are replaced with exceptions.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@vaadin-bot
Copy link
Collaborator

TC Format Checker Report - 13:44 - 26 - Jan

BLOCKER There are 1 files with format errors

  • To see a complete report of formatting issues, download the differences file

  • To fix the build, please run mvn spotless:apply in your branch and commit the changes.

  • Optionally you might add the following line in your .git/hooks/pre-commit file:

    mvn spotless:apply
    

Here is the list of files with format issues in your PR:

vaadin-slider-flow-parent/vaadin-slider-flow/src/main/java/com/vaadin/flow/component/slider/Slider.java

@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants