lifecycle
lifecycle copied to clipboard
r-lib
Manage the life cycle of your exported functions and arguments
Enable having a runnable link. Just tested this and works for me. FWIW, I have been using lifecycle from this branch from a few months, and this saves me quite...
Discovered on GitHub search, related to work on https://github.com/r-lib/lintr/issues/2113
Still missing some documentation. NB there are quite a few lints on `lifecycle` code: Lints in lifecycle code R/compat-obj-type.R:58:9: style: [lifecycle_linter] `rlang::is_na` is questioning if (is_na(x)) { ^~~~~ R/deprecate.R:288:16: style:...
The argument is not passed on to `lint_lifecycle()`.
Related to #122, the old interface will no longer be supported in the next lintr release. cf. https://github.com/r-lib/lintr/pull/2284
Related discussion in r-lib/lintr#1386. It would be nice if the `lifecycle_linter()` used in `lint_lifecycle()` could be exported and transformed to the new linter style. This would enable `lintr` to use...
Not sure if this would be as simple as adding Qq to the file pattern, or if it'd need to be parsed differently because of the possible presence of python...
The current pattern doesn't check for the end of file name, which caused my call to try reading `.Rproj` and `sysdata.rda` files. A `$` added at the end should do...
https://github.com/r-lib/lifecycle/pull/172#pullrequestreview-1709974466
