stac-fastapi.core-2.2.0 #16
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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):
Description:
Upgrade to stac-fastapi.core-2.2.0. Seems to fix the bug with the related issue. Tried to upgrade to 2.3.0 but encountered too many issues. Changes made to stac-fastapi.core affected all datetime related queries in stac-fastapi-mongo. Currently datetimes are stored as strings in MongoDB with the format provided by the users and this doesn't seem to work with the new update to stac-fastapi.core.
Also added some tweaks to the
basic_authtests so they are skipped whenBASIC_AUTHenvironment variable is not set.PR Checklist:
pre-commit run --all-files)make test)