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 often write \code{\link[pkg]{function_name}} in the documentation, so I would love to see something like @link pkg:function_name in roxygen (when pkg is omitted, we just generate \code{\link{function_name}}). This is similar to @family but allows cross references to other packages. If @link is implemented, we may want it to be automatically put into \seealso{} as well.
Currently it is still not completely clear to me how to register a custom parser like this.
The text was updated successfully, but these errors were encountered:
We talked about this a bit over email. I think it needs a slightly different syntax because it would be an inline tag, not a block tag. We couldn't think of any other use cases for inline tags, so we didn't make much progress on it.
I often write
\code{\link[pkg]{function_name}}
in the documentation, so I would love to see something like@link pkg:function_name
in roxygen (whenpkg
is omitted, we just generate\code{\link{function_name}}
). This is similar to@family
but allows cross references to other packages. If@link
is implemented, we may want it to be automatically put into\seealso{}
as well.Currently it is still not completely clear to me how to register a custom parser like this.
The text was updated successfully, but these errors were encountered: