-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Should coord_trans
be renamed to coord_transform
for API consistency?
#5825
Comments
I'm not against this, but if it is renamed we should keep The following is tangential to this particular issue. As #5821 also calls for renaming stuff, we might want to think about lifecycles of renamed functions for the future (perhaps also for {scales} palettes/transformations/label/break functions). I imagine at a certain point we might want to start discouraging using the old names of functions. The lifecycle guidance all requires changes to the function body, which is inconvenient when functions are synonyms defined as: new_name <- function(...){...}
old_name <- new_name |
I'm proposing this for tidy dev day |
No description provided.
The text was updated successfully, but these errors were encountered: