We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Request (Development) Ensure that the Pie/Donut chart legend respects sortFunction order.
Background PR1043 solved custom sorting order for Pie and Donut Charts, but did not account for altering the sort order of the Legend.
In the example below, the legend order does not respect the donut sort order.
const groupOrders = ['Amazing', 'Ok', 'Awful']; pie: { sortFunction: (a: any, b: any) => {return groupOrders.indexOf(a.group) - groupOrders.indexOf(b.group)}, }
Having an inconsistent order is a confusing user experience, which affects overall Product Experience.
The legend sort order matches the data sort order
As above
No specific timeline
If you can tell me where to look, I can play around and submit a PR.
The text was updated successfully, but these errors were encountered:
🤦♂️ Never mind. I just discovered Legend > Order.
Sorry, something went wrong.
No branches or pull requests
Summary
Request (Development)
Ensure that the Pie/Donut chart legend respects sortFunction order.
Background
PR1043 solved custom sorting order for Pie and Donut Charts, but did not account for altering the sort order of the Legend.
In the example below, the legend order does not respect the donut sort order.
Justification
Having an inconsistent order is a confusing user experience, which affects overall Product Experience.
Desired UX and success metrics
The legend sort order matches the data sort order
"Must have" functionality
As above
Specific timeline issues / requests
No specific timeline
Available extra resources
If you can tell me where to look, I can play around and submit a PR.
The text was updated successfully, but these errors were encountered: