-
Notifications
You must be signed in to change notification settings - Fork 186
'LazyData' is specified without a 'data' directory #827
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
Comments
looks like it's been there since the initial commit, probably a copy paste
vestige & unearthed by a new CRAN check? I don't see a data directory in
the tree then
…On Fri, Jul 2, 2021, 12:21 PM AshesITR ***@***.***> wrote:
From the current CRAN check results
<https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-clang/lintr-00check.html>
checking LazyData ... NOTE
'LazyData' is specified without a 'data' directory
I think removing LazyData: true from DESCRIPTION should be fine.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#827>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB2BA5PD7LREGXM5XIBLXDLTVYGTFANCNFSM47XIAPYQ>
.
|
AshesITR
added a commit
that referenced
this issue
Jul 2, 2021
* add new linters to README.md and sort the list alphabetically * provide a custom release_bullets() function for usethis::use_release_issue() * remove LazyData: true from DESCRIPTION fixes #827 * terminal newline * use rdrr links in addition to steering traffic away from datacamp-affiliated site, i think the rdrr links are better as "live" links instead of pointing to versions Co-authored-by: Michael Chirico <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From the current CRAN check results
I think removing
LazyData: true
fromDESCRIPTION
should be fine.The text was updated successfully, but these errors were encountered: