You have included the @export tag in the roxygen block for vlookup_internal(),
which will place it in the NAMESPACE with an export directive, but also
included @noRd which prevents the creation of the .Rd file for the function. So
these two are in conflict. Remove the @export tag from vlookup_in
I'm not very familiar with Roxygen, so I might be making incorrect
assumptions here.
Why are you exporting a function if it's meant to be internal?
And the @noRd would indicate that a documentation file is not created. I
would remove @noRd or @export
On Fri, Feb 24, 2023, 16:11 EcoC2S - Irucka E
If it's an internal-only function check if it's exported in your NAMESPACE
file.
On Fri, Feb 24, 2023 at 1:12 PM EcoC2S - Irucka Embry
wrote:
> Greetings, I am attaching the complete R file for your review. The
> vlookup_internal function and all of the functions in the package are
> derived fro
Greetings, I am attaching the complete R file for your review. The
vlookup_internal function and all of the functions in the package are
derived from the expss package version 0.10.7. The vlookup function was
modified in later versions so I gathered what I needed from that
previous version and
Hi everyone,
I am trying to submit a new package in CRAN. The results from devtools::check()
returned with no errors, warnings, nor notes. Upon submitting the package
tarball, i received the following error on the r-devel-windows-x86_64 version:
Flavor: r-devel-windows-x86_64
Check: whether pac
