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.
Related Issue(s):
get_collections
#320Description:
EDIT: It just occurred to me that I might be able to simplify this a bunch by just always making a warning and then configuring the
filterwarnings
setting. I am experimenting with that approach now.This PR borrows heavily from xarray and sets up a mechanism for configuring options. The idea is that by default pystac-client is flexible, but within a particular context the user can configure their settings to make pystac-client more strict.
The first options all have to do with how to respond to different events. Here's an example using on old version of earth-search that does not have a "rel=data" link defined.
Example from #320:
The individual options are modular but they could be grouped into a more succinct flag like
strict
.PR Checklist: