-
Notifications
You must be signed in to change notification settings - Fork 50
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.2enhancementNew feature or requestNew feature or requestergonomicsFeatures that improve the usability of the packageFeatures that improve the usability of the packagehelp wantedExtra attention is neededExtra attention is neededmodelsFor issues related to the pydantic models directlyFor issues related to the pydantic models directly
Milestone
Description
Recently, PR#463 has been merged with the OPTIMADE Specification.
I have therefore created this issue to keep track of the adoption of this PR in the optimade python tools.
One question I still have is whether we should return the meta field in case the optimade version is less than 1.2. A client that would specifically request version 1.2 would not understand the fields under meta. So I am wondering if we could break older clients. On the other hand, the JSON API specification does mention that there could be fields under meta so in that sense an older client could expect that there are values there.
ToDo
- : Get a basic metadata field shared.
- : Add tests for metadata field.
- : Make sure validator can handle metadata fields.
Reactions are currently unavailable
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.2enhancementNew feature or requestNew feature or requestergonomicsFeatures that improve the usability of the packageFeatures that improve the usability of the packagehelp wantedExtra attention is neededExtra attention is neededmodelsFor issues related to the pydantic models directlyFor issues related to the pydantic models directly