Pydantic validation of extensions #269
Open
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:
validate_extensions
setting that enables validation ofstac_extensions
from submitted STAC objectsusing the
stac_pydantic.extensions.validate_extensions
utility. Applicable only whenTransactionExtension
is active.
validatation
extra requirement to install additional dependencies required by extension validation (stac-pydantic
does not installrequests
andjsonschema
by default)Given that these checks do not specifically require pgstac (JSON schema validation of remote extension definitions), it could be moved to the parent
stac-fastapi
. However, I was not sure how that could be integrated since https://github.com/stac-utils/stac-fastapi/blob/main/stac_fastapi/extensions/stac_fastapi/extensions/core/transaction/client.py only contains some abstract classes. Should a mixin be used, which would be added as base class ofClientValidateMixIn
?PR Checklist:
pre-commit
hooks pass locallymake test
)make docs
)