Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slider - (re)define scope and prototype component(s) #437

Open
3 tasks
Tracked by #418 ...
thrbnhrtmnn opened this issue Oct 13, 2023 · 0 comments
Open
3 tasks
Tracked by #418 ...

Slider - (re)define scope and prototype component(s) #437

thrbnhrtmnn opened this issue Oct 13, 2023 · 0 comments
Labels
⭕ core team issue This is for the core team and should not be done by contributors 🎨 design issue Task is for designers ⌨️ dev issue Task is for developers
Milestone

Comments

@thrbnhrtmnn
Copy link
Contributor

thrbnhrtmnn commented Oct 13, 2023

Description / User Story

With this task we want to (re)define the scope of the slider and prototype the component(s).

Currently there are 4 slider variants. We should check if we can reduce the amount of Slider components and combine existing variants. After this task should have at least 2 Slider components: a single value slider (named: SliderSingleValue) and a two value slider (named: SliderTwoValues). If possible we could reduce the amount even more to only have one Slider component that covers all variants. Currently there are also separate components named SliderSingleValueWithLegend and SliderTwoValuesWithLegend, which should not exist after this issue has been solved.

We should also define i.e. how the stepper behaviour should be for the multi-value slider. One option could be, that decreasing the higher value slider so much, that the values of both sliders are identical, a further decrease via the stepper buttons would decrease both slider values. Another option would be to disable the stepper buttons once the above described scenario happens, so that a higher value slider for example can not influence the lower value slider and vice-versa. Also the stepper buttons would be disabled when the sliders are already at the highest or the lowest value that is possible.

After this task is done, the decisions need to be integrated into design and code with #268 .


Acceptance Criteria

  • The scope of the slider component(s) has been defined, it is clear how many different components we need to provide the functions we want to provide.
  • We have a prototype for the slider component(s).
  • We have a decision how the stepper button behaviour should be in the multi-value slider.

Background information

@thrbnhrtmnn thrbnhrtmnn added this to the Release 1.0 milestone Oct 13, 2023
@thrbnhrtmnn thrbnhrtmnn changed the title [Component name] - [task description] Slider - reduce amount of separate components Oct 13, 2023
@thrbnhrtmnn thrbnhrtmnn added 🎨 design issue Task is for designers ⌨️ dev issue Task is for developers labels Dec 1, 2023
@thrbnhrtmnn thrbnhrtmnn added the ⭕ core team issue This is for the core team and should not be done by contributors label Jan 5, 2024
@thrbnhrtmnn thrbnhrtmnn added this to the Release 1.0 milestone Jan 9, 2024
@thrbnhrtmnn thrbnhrtmnn changed the title Slider - reduce amount of separate components Slider - reduce amount of separate components & decide on stepper behaviour for multi value slider Jan 9, 2024
@thrbnhrtmnn thrbnhrtmnn changed the title Slider - reduce amount of separate components & decide on stepper behaviour for multi value slider Slider - (re)define scope and prototype component(s) Jan 9, 2024
@thrbnhrtmnn thrbnhrtmnn added this to the Slider milestone Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⭕ core team issue This is for the core team and should not be done by contributors 🎨 design issue Task is for designers ⌨️ dev issue Task is for developers
Projects
None yet
Development

No branches or pull requests

1 participant