-
Notifications
You must be signed in to change notification settings - Fork 234
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
Links in @family tag don't have anchors #1650
Comments
Apologies, I think they are not needed in this case (yet?) because the links are always to topics in the same package and CRAN doesn't complain about it. I am not sure if then the anchors are needed according to the documentation. I leave it open in case this helpful or you want to harmonize both ways have links. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CRAN (and Bioconductor) wish that all cross-references were anchored (And testing via a new environmental variable).
I was checking the current state of CRAN's cross references and I found out that some of my own cross-references were missing the anchor (See for example the source and the output). This happens when they are generated with
#' @family group
.Created on 2024-08-27 with reprex v2.1.1
I think the root cause is that it is handled different than in other cases where links are created (as in markdown it works well), see:
roxygen2/R/rd-family.R
Lines 56 to 60 in 9652d15
Different from:
roxygen2/R/object-import.R
Lines 36 to 41 in 9652d15
I'm not sure how it handles multiple topics in the same file after #1109 or how to find the right topic on the rd-family.R, but fixing this will eventually help solve a note from packages that use roxygen2.
The text was updated successfully, but these errors were encountered: