-
Notifications
You must be signed in to change notification settings - Fork 333
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
Re-exporting non-function object (?) breaks build_site() #666
Comments
The problem is here: Line 100 in 90867f9
This assumes that we are re-exporting a function, but in my case it is an object... the solution is to find where the object was imported from. This is not always easy, because we might import a whole package.... but it is not bad at least for |
We cannot take the package name from the environment of the function in this case, but need to look at the import env of the package. Fixes #666.
We cannot take the package name from the environment of the function in this case, but need to look at the import env of the package. Fixes #666.
We cannot take the package name from the environment of the function in this case, but need to look at the import env of the package. Fixes #666.
We cannot take the package name from the environment of the function in this case, but need to look at the import env of the package. Fixes #666.
We cannot take the package name from the environment of the function in this case, but need to look at the import env of the package. Fixes #666.
I'm hitting this documentation issue with reexported functions in a couple of my packages. Is there a way to improve the error message to potentially tell you which line contains the offender? This is currently difficult to diagnose for long vignettes and/or package NEWS files. Seems like it might be this code, correct? Here's an example:
@gaborcsardi can we reopen this or should I start a new issue? |
Alternatively, is there a way to disable automatic function links when building a pkgdown site? |
This is callr, which now re-exports
process
from processx. If I remove theexport(process)
fromNAMESPACE
then it works fine.The text was updated successfully, but these errors were encountered: