New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the OptimadeMetaResponse to development schema #13
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ml-evs !
Just a few minor requests - some of which may not even be addressed in this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ml-evs, please refactor into the different models submodules.
e62b715
to
f99cedf
Compare
bf5d5a9
to
77ebdaf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Minor request: let's explicitly link to the 1.0 JSON API spec, e.g. https://jsonapi.org/format/1.0/#document-meta
I guess we should do this in the spec too! |
@ml-evs I left a few comments above, just wondering whether you were planning to address them / whether you think those don't belong here... |
I've responded to each and resolved, while relevant I don't think they belong in this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @ml-evs !
This PR updates the
OptimadeMetaResponse
class to reflect the current state of the development schema, adding theOptimadeProvider
class.