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
Set correct meta->schema
value automatically
#1323
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.
I noticed you have not added any tests. Do you think it would be possible/worthwhile to do so ?
0e54d6a
to
cb96146
Compare
cab3f7c
to
6655e0c
Compare
Done! |
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 good to me.
Codecov Report
@@ Coverage Diff @@
## master #1323 +/- ##
==========================================
- Coverage 91.49% 91.46% -0.04%
==========================================
Files 72 72
Lines 4364 4368 +4
==========================================
+ Hits 3993 3995 +2
- Misses 371 373 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
This PR adds a config option that tracks whether the reference server is in index or non-index mode, then uses that to correctly set the
meta->schema
value in that server's responses.This means that a value no longer needs to be provided to the
meta_values
function if not necessary (see aiidateam/aiida-optimade#375).Also tweaks the OpenAPI schema with a formatting change due to dependency updates.