-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Synchronise lifecycle management #6733
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
Conversation
R/utilities.R
Outdated
| defunct <- "3.0.0" | ||
| full <- "3.4.0" | ||
| soft <- packageVersion("ggplot2") |
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.
Just increment versions here if advancing the lifecycle.
thomasp85
left a comment
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.
The escalate argument is useful for when you want to, well, escalate a deprecation. It would be nice if deescalation was possible as well, e.g. keep something on soft even though we move the marker beyond that version threshold
I agree that this would be nice to have, but doing it should be discouraged. I've added an option to postpone a cycle. |
Merge branch 'main' into lifecycle_manager # Conflicts: # R/aes.R
|
Found a few cases of |
This PR aims to fix #6731.
It replaces the
deprecate_warn0()anddeprecate_soft0()internal functions with a new function:deprecate().If we want to advance the lifecycle of deprecated functions, we just need to edit the versions in
deprecate()instead of finding an replacing functions all over the place. There is also an option to escalate a deprecation to defunct or warning ahead of the cycle.