Skip to content
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

Compatibility with incoming ggplot2 changes #2368

Merged
merged 3 commits into from
Sep 3, 2024

Conversation

teunbrand
Copy link
Contributor

@teunbrand teunbrand commented Jul 19, 2024

Hi Carson and other maintainers,

Apologies for the cold PR!
While building a new feature in ggplot2 we found through reverse dependency checks that {plotly} was negatively affected by the changes we'd like to implement. The new feature makes extensive use of computed values in the Geom$default_aes field, contrasted by mostly fixed values in the current CRAN version. Mostly, this PR resolves the relevant defaults before using them in {plotly}. The changes herein should be backwards compatible (locally tested with ggplot2 3.5.1).

In addition, a small change with regards to label setup is sneaked in for good measure.
If you rather have a separate PR for that I'll prepare one.

We don't intend to release a new version of ggplot2 this year, so there isn't much of a hurry to merge this.

@cpsievert
Copy link
Collaborator

Apologies for the cold PR!

I very much appreciate it -- well done, thank you!!

@cpsievert cpsievert merged commit a7a0652 into plotly:master Sep 3, 2024
@teunbrand teunbrand deleted the ggplot2_3_6_0_compat branch January 31, 2025 08:47
@teunbrand
Copy link
Contributor Author

Hi @cpsievert, we're aiming for a ggplot2 release before summer (around May). I'd be swell if there'd be a compatible plotly version out around that time :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants