-
Notifications
You must be signed in to change notification settings - Fork 142
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
[Bug] Fix display of marks in vm.Slider
and vm.RangeSlider
#613
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for getting to the bottom of this and fixing it! Super clear dev example also - I love the containers with title which is much better than me getting confused about which row is which 😅 🤦
Just a couple of things about the tests but otherwise looks great.
vizro-core/tests/unit/vizro/models/_components/form/test_range_slider.py
Show resolved
Hide resolved
vizro-core/tests/unit/vizro/models/_components/form/test_range_slider.py
Outdated
Show resolved
Hide resolved
vizro-core/tests/unit/vizro/models/_components/form/test_range_slider.py
Outdated
Show resolved
Hide resolved
vizro-core/tests/unit/vizro/models/_components/form/test_range_slider.py
Outdated
Show resolved
Hide resolved
…_slider.py Thanks!! I like the first 👍 It prints out the types as well. Co-authored-by: Antony Milne <49395058+antonymilne@users.noreply.github.com>
… into bug/fix-slider-type
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. 🙌
Description
Closes: #612: Previously, our marks were converted to integers, leading to incorrect value displays. This, combined with an existing bug in Dash, caused the marks to be displayed incorrectly.
vm.Slider
andvm.RangeSlider
@nadijagraca - I noticed that we previously had the typing
marks: Optional[Dict[float, str]]
, but it was changed in this PR: #230. Do you remember the reason for this change? I couldn't reproduce the original bug that the PR fixes, so I'm uncertain if reverting to the original typing will cause any issues. Could you also take a look? 🤔Screenshot
Notice
I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":