Skip to content

Topics marked with @noRd still generate link resolution warnings #1730

@DavisVaughan

Description

@DavisVaughan

In vctrs, this block

https://github.com/r-lib/vctrs/blob/65e335e3e1f9136ccf31c4ea755aa7007842adb0/R/dim.R#L15-L24

generates this warning with CRAN roxygen2 7.3.3

✖ [dim.R:15](vscode-file://vscode-app/Applications/Positron.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/workbench.html#): @seealso Could not resolve link to topic "dim2" in the dependencies or base packages.
ℹ If you haven't documented "dim2" yet, or just changed its name, this is normal. Once "dim2" is
  documented, this warning goes away.
ℹ Make sure that the name of the topic is spelled correctly.
ℹ Always list the linked package as a dependency.
ℹ Alternatively, you can fully qualify the link with a package name.

It feels like it should have been exempt from this because it is @noRd?

I can easily change this too on our end, but wanted to bring it up

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions