-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Check for dropped aesthetics #4866
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
Check for dropped aesthetics #4866
Conversation
…opped that shouldn't be. Fixes tidyverse#3250.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally looks good - should we update the docs for the affected stats to say that these aesthetics are dropped? Seems like a nice thing to do
Let me think about documenting the dropped aesthetics. In some cases it's just a temporary variable that gets dropped, so documenting that is not so useful. In other cases (e.g. |
yeah - "thankfully" the stats aes documentation is not automatic so it is just a matter of cherry picking where to add it to the docs |
@clauswilke is it possible to get the docs updated soon? I plan to start the release process soonish to give the revdep maintainers the summer to fix potential issues |
@thomasp85 I think I can do it today. I was waiting for you to merge the vctrs PR, but that has happened, correct? |
Ah, sorry -- I missed that. Yes, vctrs has been merged in |
@thomasp85 I think I've addressed everything. I documented the stats where it seemed appropriate. In particular, I didn't document |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Check for dropped aesthetics and issue a warning if aesthetics are dropped that shouldn't be. Fixes #3250.
As a consequence of this change, stats now need to advertise which aesthetics they are dropping, via the new
dropped_aes
field. If they don't, unit tests may fail because code now generates warnings that previously ran quietly.Example of the new feature:
Created on 2022-06-09 by the reprex package (v2.0.0)