alternative to path_package()

[sbgraves237]

In my new package "github.com/sbgraves237/SS4Maddison", I want to store raw data file in my local environment and use it in a vignette when available and skip processing it when it's not available. My current solution starts with putting it in "inst/extdata" on my local computer and listing it in "inst/extdata/.gitignore". Then I wrote "path_package2" inspired by the description of "fs::path_package()" in section 7.3.1 Filepaths of R Packages. My "path_package2" returns a character vector of full.names of all files found with an attribute "searched" giving the full.names of all directories searched: If the character vector is of length 0, I can skip the parts of the vignette requiring that data file. It seems to work as desired regardless of which state the package is in. And the vignette source could be copied out of the package into another directory with the the desired data file somewhere close, and "path_package2" could find it if it's enough in some appropriate sense.

What do you think?

Please feel free to "path_package2" or the ideas behind it if they appeal to you. Spencer Graves (sbgraves237).

[vishalmzp001-ship-it]

Thank you for sharing your approach! From a non-developer/user perspective, what are the main benefits and risks of using your new path_package2() method compared to the standard way? For example, will it affect package speed or stability?"

[sbgraves237]

Within RStudio, the working directory is different when I execute the code line by line vs. when I knit the vignette or build or check the package. That created problems that I solved with this function. The tidyverse may already have another way to solve this problem, I couldn't find a better way, so I wrote this. Thanks for asking. Spencer Graves.

[vishalmzp001-ship-it]

detailed explanation, Spencer."