Fixed bugs in mpl colorbar arrows and Image.range #1211
Merged
Conversation
This file contains 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
|
Tests have passed. Ready to merge? |
|
Yes, ready to merge, I'll open the related issue now. |
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.
In fixing a bug in the colorbars (#1109) I found a bug in handling partially bounded Dimension.range settings, e.g.:
Would report
(0, 3)when all our other Elements respect explicitly set ranges. I'll probably open another PR to add an argument to the range method to ignore thesoft_rangeandrangeon the Dimension. Knowing the actual data range is perhaps more useful and we should consider returning that by default and only returningDimension.rangewhen requested, which all the plotting code could do.