Put back LazyData, remove refinery from NAMESPACE #6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks. I think I will need to add "refinery" back into the NAMESPACE for a check we need but don't run on CRAN. However, there could be a hidden character someplace in what we read as "refinery". ??? Otherwise, I have another problem I don't understand. Spencer |
|
You can have it in NAMESPACE if you save the object in R/sysdata.rda, or create it in code in some .R file in the R directory. It doesn't really make sense to use sysdata.rda, since "this is intended for system datasets that are not intended to be user-accessible via data" (WRE, section 1.1.5). |
|
changes per Duncan Murdoch. Thanks. Spencer Graves |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.