Compatibility with ggplot2 4.0.0 #319
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you @teunbrand I'll make sure to send the cran update when ggplot2 new release will be on cran. David |
|
Sounds great, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi there,
We've been preparing for a new major release of ggplot2 and ggiraph showed up on the reverse dependency checks.
This PR contains the changes that would maintain compatibility with ggiraph and ggplot2 for the new version.
The main change in ggplot2 that affects ggiraph is that the
Geom$default_aesfield contains more unevaluated expressions than before.We hope to send the release to CRAN sometime soon.
Best wishes,
Teun