Skip to content

v0.2.0

Compare
Choose a tag to compare
@CasperWA CasperWA released this 07 Sep 19:36
· 202 commits to main since this release

Re-design - remove gateway-as-an-OPTIMADE-DB

With the merge of #82, the repository has been slightly re-designed to optimize its purpose and base code.

Instead of having every dynamically generated gateway have its own OPTIMADE DB representation, with all the valid introspective endpoints etc., it is simply another resource. This focuses the package to conduct all queries using the QueryResource - minimizes the code and confusion, and should make the usage easier to grasp.

The proper entry points to using the gateway service is to go through GET /search or POST /search and that's it.
All other endpoints are service or semi-introspective endpoints that the gateway uses internally (/databases, /gateways) or the user is sent to when receiving their query results (/queries). No more - no less.

It is still possible to return a response that will validate as an OPTIMADE response by using the as_optimade=True URL query parameter in the GET /search endpoint directly. Or one can go via Python; instantiate the finalized QueryResource (via GET /queries/<ID>) and use the response_as_optimade() method.
In order to keep the ids unique in the OPTIMADE-valid response, they are all prepended by <provider-prefix>/<database-id>/.

Changelog

v0.2.0 (2021-09-07)

Full Changelog

Implemented enhancements:

Fixed bugs:

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator