Rangeslider data conversion #441
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mdtusz
added
bug
mdtusz
force-pushed
the
rangeslider-datafix
branch
2 times, most recently
from
2aedde7 to
fb640f6
Compare
mdtusz
force-pushed
the
rangeslider-datafix
branch
from
fb640f6 to
ca7c175
Compare
|
💃 nicely done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, range sliders did the conversion of data to points on it's own. This changes it so that the slider will use the existing axis data conversion methods and work when only a single axis' data is given e.g.
Fixes #435