Warning for unknown topic in internal noRd page

[MichaelChirico]

When writing @noRd documentation, I didn't expect roxygen2 to actually check it with any real vigor, but updating to 7.3.3 found a new issue:

#' @param See [other_undocumented_function()]
one_internal_function <- function() ...

Now produces a warning like:

✖ get_source_expressions.R:277: @param Could not resolve link to topic "other_undocumented_function" in the dependencies or base packages.
ℹ If you haven't documented "other_undocumented_function" yet, or just changed its name, this is normal. Once "other_undocumented_function" 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.

Is this WAI?

[mccroweyclinton-EPA]

I too am getting this warning with the recent release of Roxygen2. I believe it has something to do with the order of the Collate fields in the project description. Unfortunately I have no recourse as to how to fix this since my code requires my collate field to stay as it is. My suggestion is to either perform this check as a very last step in the oxygenize process or to add a tag that allows the developer to suppress this warning.

[DavisVaughan]

Another example #1730