8000 Issues when using package external data as internal · Issue #64 · yonicd/sinew · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Issues when using package external data as internal #64

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.

Sign up for GitHub

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

Jump to bottom
Open
GitHunter0 opened this issue Nov 6, 2020 · 0 comments
Open

Issues when using package external data as internal #64

GitHunter0 opened this issue Nov 6, 2020 · 0 comments

Comments

@GitHunter0
Copy link
GitHunter0 commented Nov 6, 2020 •
edited
Loading

In R packages, it is possible to use external data as internal data (i.e. use data exported by my package in my own package functions). This can be done by this syntax my_package::my_external_data (see link below):
https://coolbutuseless.github.io/2018/12/10/r-packages-internal-and-external-data/

However, in doing that, sinew interprets that my_package is a third-party package, then adds it on DESCRIPTION "Imports" and on Roxygen comments (@Importfrom my_package my_external_data), which leads to circular references and errors from CMD Check.

The solution I believe is to simply program to add nothing when the name of the package is the same of the package you are creating.

Thank you.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GitHunter0
0