Skip to content
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

Running load_all() twice moves devtools_shims on the search path #265

Open
moodymudskipper opened this issue Nov 25, 2023 · 0 comments
Open

Comments

@moodymudskipper
Copy link

moodymudskipper commented Nov 25, 2023

To re produce, within any package project (named PACKAGE below) :

devtools::load_all(".")
#> ℹ Loading PACKAGE
search()
#>  [1] ".GlobalEnv"        "devtools_shims"    "package:PACKAGE"  "package:testthat"  "tools:rstudio"     "package:stats"    
#>  [7] "package:graphics"  "package:grDevices" "package:utils"    "package:datasets"  "package:methods"   "Autoloads"        
#> [13] "package:base"    
devtools::load_all(".")
#> ℹ Loading PACKAGE
search()
#>  [1] ".GlobalEnv"        "package:PACKAGE"   "devtools_shims"    "package:testthat"  "tools:rstudio"     "package:stats"    
#>  [7] "package:graphics"  "package:grDevices" "package:utils"     "package:datasets"  "package:methods"   "Autoloads"        
#> [13] "package:base"   

The second situation is actually better, because the package might implement its own versions of functions that end up in devtools_shims, making it challenging to work with this workflow.

I personally have this challenge as I redefine ? in a package. Could we make the 2nd behavior above the unique one ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant