You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will make sense once ODK Central has reached 1.0 and development slows down.
Until then, ODK Central will add features to its API, and ruODK targets the latest ODK Central version (as indicated by mirroring the major/minor version numbers).
Suggestion: the best approach until 1.0 is to test the real deal and run tests uncached against the latest ODK Central instance run by ODK themselves. If those tests work, ruODK will be O(D)K.
The text was updated successfully, but these errors were encountered:
I don't think the large size of the cassettes (cached http responses) affects r check, e.g., the cassettes directory in this package https://github.com/ropensci/rgbif/ is 32 MB, but running check on it throws no notes/warnings/etc - But i could be wrong - if size of cassettes is a concern, one option is to skip tests on CRAN for which cassettes are too large to include in the pkg, and those cassette files added to .Rbuildignore
Feature
Logging this idea for future Florian:
https://devguide.ropensci.org/building.html#recommended-scaffolding
This will make sense once ODK Central has reached 1.0 and development slows down.
Until then, ODK Central will add features to its API, and ruODK targets the latest ODK Central version (as indicated by mirroring the major/minor version numbers).
Suggestion: the best approach until 1.0 is to test the real deal and run tests uncached against the latest ODK Central instance run by ODK themselves. If those tests work, ruODK will be O(D)K.
The text was updated successfully, but these errors were encountered: