Skip to content

Introducing multi-legend feature from plotly.js v2.22 will lead to breaking changes #406

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

Closed
kMutagene opened this issue Jul 26, 2023 · 1 comment

Comments

@kMutagene
Copy link
Collaborator

kMutagene commented Jul 26, 2023

Just adding this as an issue to the milestone so it is immediately visible.

This means that all new upstream feature additions will be on v5, which will then most likely have some preview versions again until it is completely up-to date with plotly.js

@kMutagene kMutagene added this to the Plotly.NET 5.0 milestone Jul 26, 2023
kMutagene added a commit that referenced this issue Oct 23, 2023
- extend SubplotId with Legend case
- getting, setting, and updating multiple Legend objects on the Layout
- setting Legend anchor on traces
@kMutagene
Copy link
Collaborator Author

kMutagene commented Oct 23, 2023

still to-do:

  • dedicated legend field on all trace constructors
  • tests

kMutagene added a commit that referenced this issue Oct 24, 2023
- this enables setting legend anchors on trace generation
- additionally, fix `coloraxis` atribute name on some 3D traces
kMutagene added a commit that referenced this issue Oct 24, 2023
- fix `font` and `borderwidth` attributes of legends having switched names
- this commit contains backwards incompatible changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant