Should coord_trans be renamed to coord_transform for API consistency?

[davidhodge931]

No description provided.

[teunbrand]

I'm not against this, but if it is renamed we should keep coord_trans() around for backward compatibility.

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

[teunbrand]

I'm proposing this for tidy dev day