react-component / react-component/slider
Customized Range - Update both LowerBound and UpperBound
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.1k
- Forks
- 768
- Avg merge
- 11d 22h
- Merged PRs (30d)
- 5
Description
Not quite sure if this is a feature or bug.
To replicate, on the "Customized Range" example:
- Set the LowerBound to 0 and UpperBound to 20. Apply
- Set the LowerBound to 30 and UpperBound to 50. Apply
The LowerBound on the slider will remain at 20.
Look like Range.ensureValueNotConflict will keep the LowerBound at previous UpperBound if "allowCross is false" even though UpperBound is also updated and vice versa
Set "allowCross to true" will make it work, but obviously not ideal
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Customized Range example and trace Range.ensureValueNotConflict, focusing on updates where allowCross is false. Reproduce the two successive LowerBound and UpperBound changes, then verify that both slider handles reflect the latest applied values without enabling allowCross.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100