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
export proj_path #415
Comments
The party line on that in usethis itself is that end users are supposed to use rprojroot (or here) to build paths within a project. Do you think that also applies to you (or, more generally, developers of packages that use usethis) or is the situation different? If I export |
I see, I guess this makes sense, you can close this if you don't think it is worthwhile. |
I think it probably does make sense to export it, for use in other packages. It just comes with same risk / downsides as exporting |
* Rearrange this file * Export proj_path() Fixes #415 * NEWS bullet
For devtools I often need to construct the full paths to files inside a package, so it would be useful to have
proj_path()
exported so I wouldn't have to use something likefile.path(usethis::proj_get() ...)
.The text was updated successfully, but these errors were encountered: