-
Notifications
You must be signed in to change notification settings - Fork 83
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
Allow user-defined offset #157
base: dev
Are you sure you want to change the base?
Conversation
Error in the Travis CI build in the read.socrata examples... I can't figure out exactly what is going on, and can't seem to reproduce this on my forked version. Any tips?
|
@flynn-d - thank you for your pull request. This is very promising. I re-ran the tests with slightly different errors:
All of them pertain to the |
Hi Tom -- As far as I can tell, these are all messages resulting from test which expect_error, and these warning messages appear. I ran devtools::test() on the master branch, and got the same messages as you see here. These don't appear to be why it failed (but might be additional issues also!). Poking around, I saw the same I appreciate your guidance -- I'm finding this type of error for many packages testing on r-devel, e.g. search |
@flynn-d - just getting to review the code (sorry for the delay). User offset is great, but should this feature be paired with user-defined The 50,000 limit is because that's the maximum of the version 2.0 of the SODA API. However, version 2.1 does not have a limit. Let me know if you think I'm off with my thinking on this. |
Tom, great idea, I'll work on that and update. Still unclear about the r-devel issue, but will give it a try. |
Building off of #154, and also a prior PR #127, this change allows users to pass offsets as the queries. This skips paging and gives a message that the query has been offset.
I'll keep working on this if it breaks any of the current tests.