Setting a new min/max value for a numeric slider causes an exception
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 317
- Forks
- 19
- Avg merge
- 14m
- Merged PRs (30d)
- 3
Description
When trying to update a numeric slider (only tested on IntRangeSlider) and the min or max value is update, it causes a traitlets.traitlets.TraitError.
Case where new min > current max:
https://github.com/user-attachments/assets/28842a11-1222-4f14-bac0-ef13619008d6
The order of the attributes being input set seems to mitigate the issue:
https://github.com/user-attachments/assets/629b4b10-6381-4019-995c-6f182ccb7170
But if you update to a different value, it can still break. Case where new max < current min:
https://github.com/user-attachments/assets/2f80a9dc-3d98-423e-9339-69cadd282520
I would think these lines would handle catching that?
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
The reported path is reacton/core.py around lines 1980-1985; start by reproducing the IntRangeSlider min/max updates described in the issue, including both invalid intermediate orderings. Done means changing min or max in these cases no longer raises TraitError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100