-
Notifications
You must be signed in to change notification settings - Fork 45
fix: fields extension on collections endpoint #326
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
Conversation
e4c9d3c to
4aa6542
Compare
f0fbab4 to
a915f2a
Compare
4b57864 to
b5e71b4
Compare
b5e71b4 to
04600a3
Compare
d1df3ca to
4452922
Compare
hrodmn
left a comment
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.
Thanks for fixing this @alukach!
This comment was marked as off-topic.
This comment was marked as off-topic.
I see you marked this comment as off-topic, but I will share that I was going off of: https://github.com/stac-api-extensions/collection-search/blob/v1.0.0-rc.1/README.md?plain=1#L103-L108 |
Related Issue(s):
Description:
Currently, the
fieldsextension fails on the Collections endpoint due to the fact that we process theincludeandexcludearguments asset()values and then attempt to convert it to JSON.setvalues are not supported byjson.dumpsand thus an error is thrown.stac-fastapi-pgstac/stac_fastapi/pgstac/core.py
Lines 81 to 103 in 990b2af
stack trace
This PR converts these values to a
listbeforejson.dumps().Additionally, I have added a test to validate this behavior. #327 and #328 came out of these tests, requiring the testing to be adjusted slightly.
PR Checklist:
pre-commithooks pass locallymake test)make docs)