-
Notifications
You must be signed in to change notification settings - Fork 51
Support for OPTIMADE v1.2.x #1419
Copy link
Copy link
Open
Labels
OPTIMADE v1.2This label describes actions that have to be taken to be complient with OPTIMADE 1.2This label describes actions that have to be taken to be complient with OPTIMADE 1.2help wantedExtra attention is neededExtra attention is neededschemaConcerns the schema modelsConcerns the schema models
Milestone
Description
Metadata
Metadata
Assignees
Labels
OPTIMADE v1.2This label describes actions that have to be taken to be complient with OPTIMADE 1.2This label describes actions that have to be taken to be complient with OPTIMADE 1.2help wantedExtra attention is neededExtra attention is neededschemaConcerns the schema modelsConcerns the schema models
This issue is for tracking our support with the upcoming release candidates of OPTIMADE v1.2. There are several issues/PRs tagged under the OPTIMADE v1.2 label
and milestone.
We should collect all the PRs in a separate branch for v1.2 features before merging them into master. This will allow us to create the v1.2 OpenAPI schemas for the specification release (without necessarily having all PRs finished, fully-tested and released).
As all of the functionality in 1.2 is both optional and backwards compatible with 1.1, I don't think we necessarily need to go down the namespace package route and maintain support for older 1.1 models/servers, though it may be useful to begin thinking about it for future versions (especially the client and the validator, which could be pointed at older versions of the models for deserializing the response from other implementations). This would require an overhaul of our CI that I don't think we really have the resources to do at the moment; instead it may be easier to patch the validator/client to work differently depending on the API version returned by the implementation.