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'd like to make a case for an argument default_packages = getOption("reprex.default_packages") .
When loading conflicted, all those nasty deprecation warnings disappear
The number one issue for repeating the generation of a reprex is to forget to attach magrittr
Granted, the second issue is losing relevance with |>, but I would totally use options(reprex.default_packages = c("conflicted", "magrittr")) . The inserted library() calls would be inserted in front of the code that is copied from the clipboard.
Would you like to review a PR?
library(dplyr)
#> #> Attaching package: 'dplyr'#> The following objects are masked from 'package:stats':#> #> filter, lag#> The following objects are masked from 'package:base':#> #> intersect, setdiff, setequal, union
I'd like to make a case for an argument
default_packages = getOption("reprex.default_packages")
.Granted, the second issue is losing relevance with
|>
, but I would totally useoptions(reprex.default_packages = c("conflicted", "magrittr"))
. The insertedlibrary()
calls would be inserted in front of the code that is copied from the clipboard.Would you like to review a PR?
Created on 2022-06-24 by the reprex package (v2.0.1)
Created on 2022-06-24 by the reprex package (v2.0.1)
The text was updated successfully, but these errors were encountered: