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
Other than hosting the (OpenAPI) schemas, is this repository also meant to host the source of those schemas, i.e., the Python models made in optimade-python-tools?
The text was updated successfully, but these errors were encountered:
IMO the schema "source" belongs in the main OPTIMADE repo alongside the specification, so that we in the future can find a workflow that keeps the schemas and the specification text in sync. Our present workflow of delaying the schema updates to just before releases is not a good idea. It requires duplicate work, is error-prone, and makes it difficult to test-implement features from the develop version.
What I hope to move over to at some point post-v1.0 is that we simply tag up the specification so that we instead can generate the OpenAPI schemas straight out of the specification rst file, rather then go via optimade-python-tools. Having spent some time with the OpenAPI schemas preparing Materials-Consortia/OPTIMADE#303, this seems fairly straightforward to set up.
Other than hosting the (OpenAPI) schemas, is this repository also meant to host the source of those schemas, i.e., the Python models made in
optimade-python-tools
?The text was updated successfully, but these errors were encountered: