You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The deployed version of the API that I saw this on was based on this branch so I don't know if this is also true on master. If not I won't be offended by a quick close.
The text was updated successfully, but these errors were encountered:
This was fixed, but a regression that was introduced in a recent refactor.
The response model for the collections endpoint is Collections, which is the correct format; however, all_collections on the backends and the base class (
This should instead construct a stac-pydantic Collections object or a TypedDict with the appropriate entries, and return with the appropriate links (see the PC endpoint for reference)
This could either be solved by changing the all_collections signature and modifying the backend core clients, or translating the list of collections at the API level so that all backends use the same logic to construct the Collections response
The
/collections
route according to the API spec returns an object withcollections
andlinks
keys --The deployed version of the API that I saw this on was based on this branch so I don't know if this is also true on
master
. If not I won't be offended by a quick close.The text was updated successfully, but these errors were encountered: