Uh oh!
There was an error while loading. Please reload this page.
Legend rank per pie slice - #7723
Conversation
Each entry then corresponds to one slice.
my-tien
commented
Mar 4, 2026
my-tien
commented
Apr 27, 2026
I fixed the baseline-b64 test mentioned in my previous comment. This time the failed baseline test seems to contain only minimal pixel differences. Any advice here? @emilykl |
my-tien
commented
Apr 27, 2026
Sorry for the spam, I saw that kaleido was bumped for the CI pipeline which explains the pixel differences. I updated the baseline image. All good from my side! Should I look into the failed flaky test? Or do you think this is fine? |
emilykl
commented
Apr 28, 2026
Hi @my-tien ! Don't worry about the flaky test for now, you're right that it's unrelated to this PR. Could you link an issue to this PR? You can open a new one if needed. I'm OK with this change, but could you explain why it's better for you to use |
my-tien
commented
Apr 29, 2026
Thanks Emily, I forgot to create an issue for this, sorry. I now added an issue and linked it in the Pull Request description. I tried to explain the issue there. Let me know if I should add anything to it! |
emilykl
commented
Apr 30, 2026
Thanks @my-tien! The justification in the linked issue makes sense, I had forgotten that pie legend entries sort automatically by value. Could you rename the image mock and baseline image to remove the initial |
Uh oh!
There was an error while loading. Please reload this page.



This PR makes it possible to pass arrays to the pie property 'legendrank' so that legend rank assignment can be configured per slice.
Changes:
Previously,
traces.pie.legendrankonly accepted one value that applied for all slices. With this PR, slice legend entries can be individually ranked in the legend. E.g. the below JSON would produce the displayed chart:This fixes#7778
Note:
This feature is not expected to work when pie
valuesare not set.Disclaimer
I am required to add that…the software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. in no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software.