-
Notifications
You must be signed in to change notification settings - Fork 48
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
Remove default limit #584
Remove default limit #584
Conversation
We should trust the server to know how many things it will response with.
a16500e
to
692550a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I like this. That limit always seemed weird to me
Codecov ReportPatch coverage is
📢 Thoughts on this report? Let us know!. |
@gadomski can you share a bit more (here or in the docs) about how this changes the behavior (maybe depending on how the sever is behaving w.r.t.
Is that part of the response body to |
Sure ... this PR changes behavior so that pystac-client, by default, does not send a
Configuration in the server, e.g. for stac-fastapi it's 10: https://github.com/stac-utils/stac-fastapi/blob/main/stac_fastapi/types/stac_fastapi/types/search.py#L125 |
Ok, thanks. Looks like on the Planetary Computer, we have it set to 250: ❯ curl --silent "https://planetarycomputer.microsoft.com/api/stac/v1/search" | jq '.features | length'
250 Following the guidance of the server (by default) makes sense to me. |
Related Issue(s):
Description:
We should trust the server to know how many things it wants to respond with. Tagging in a couple of folks for reviews since this is changing default behavior. I don't think this is worth marking as a breaking change (thereby forcing a v0.8), but happy to be convinced otherwise.
PR Checklist: