-
Notifications
You must be signed in to change notification settings - Fork 29
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
Indicate the the 'observation search' request takes pagination parameters. #389
Conversation
…ters. Assuming I'm reading the source correctly, this request does honor these parameters: https://github.com/inaturalist/iNaturalistAPI/blob/30987c8fe5b00b8a56ad7eb96c44402530efa5d6/openapi/schema/request/observations_search.js#L282-L296
Hmm this might not be this simple, since the 'observation observers' endpoint also has iNaturalistAPI/lib/views/swagger_v1.yml.ejs Lines 995 to 1004 in 30987c8
...but has a different set of expected parameters:
|
Could you please be more clear about what the problem is that this PR is attempting to fix? The title says Specifically what endpoints (including API version) don't document pagination parameters but should? |
@pleary If I recall correctly, I ran into this when using the |
And agreed the way I worded the original issue was not clear, sorry about that! |
I pushed a commit fbcb988 where I explicitly add the We have several endpoints that share a lot of the same parameters for filtering data, but not some of the more usability oriented parameters like ordering and sorting. OpenAPI/swagger doesn't have a great way of supporting the idea of reusable subsets of parameters, so the implementation here isn't as clean as I'd prefer. Thanks for making the pull request and raising the issue about the undocumented parameters! |
Perfect! Thank you so much @pleary 🌻 |
Assuming I'm reading the source correctly, this request does honor these parameters:
iNaturalistAPI/openapi/schema/request/observations_search.js
Lines 282 to 296 in 30987c8