You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was asking because the warning generated would encourage the user to report any deprecation warning ("the issue") as GitHub issue, e.g.
The trust argument of import() should be explicit for serialization formats as of rio 1.0.3.
ℹ Missing trust will be set to FALSE by default for RDS in 2.0.0.
ℹ The deprecated feature was likely used in the rio package.
Please report the issue at https://github.com/gesistsa/rio/issues.
The text was updated successfully, but these errors were encountered:
I think there is no bug in lifecycle. Take a look at the env, user_env arguments. If the function is called directly, you will not see a deprecation warning
Pair of environments that define where deprecate_*() was called (used to determine the package name) and where the function called the deprecating function was called (used to determine if deprecate_soft() should message).
These are only needed if you're calling deprecate_*() from an internal helper, in which case you should forward env = caller_env() and user_env = caller_env(2).
Otherwise, lifecycle detects that a package internally uses a deprecated feature and hence throws a warning that encourages a bug report
Thank you very much for the package. I was wondering is there a way to skip the
footer()
call herelifecycle/R/deprecate.R
Line 248 in 77fce9b
I was asking because the warning generated would encourage the user to report any deprecation warning ("the issue") as GitHub issue, e.g.
The text was updated successfully, but these errors were encountered: