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.
sort categorical Cartesian axes by value #3864
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
sort categorical Cartesian axes by value #3864
Changes from 4 commits
9c09d8c
2d379f7
e4e5eaa
76683ba
fac239b
67cc14d
c6e049b
7c8d52b
54b3ff9
9aaa10b
553e193
bf6bdf3
d13542e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Hmm. I don't understand why the categories show up as
[b, c, a]
. Shouldn't they
values for the bar trace by considered also?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.
At the moment, not if they are on a different axis: only the traces associated with the axis to be sorted are accounted for. In this mock, the
bar
trace is on different axes namely(x|y)axis2
. It ends up inheriting the order of categories ofxaxis
because itmatches
it but that's all. I thought this behavior would be useful.We could account for the values of all traces across all matching axes IF we also support a way to specify traces to ignore as suggested by @nicolaskruchten (see #3606 (comment)) so that we can reproduce the current baseline.
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.
Thanks for the explanation. That makes perfect sense 👍