-
Notifications
You must be signed in to change notification settings - Fork 44
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
Small code corrections #1562
Small code corrections #1562
Conversation
# Conflicts: # openapi/openapi.json # optimade/models/__init__.py # optimade/models/jsonapi.py # optimade/models/structures.py # optimade/server/mappers/__init__.py # optimade/server/middleware.py # optimade/server/routers/info.py # optimade/server/routers/utils.py # optimade/server/schemas.py # optimade/server/warnings.py # optimade/validator/config.py # requirements.txt # setup.py # tests/server/conftest.py # tests/server/test_mappers.py
-query_parameters flag and removed config_file field from default config example.
…om default config example.
…/JPBergsma/optimade-python-tools into JPBergsma/small_code_corrections
# Conflicts: # openapi/openapi.json # optimade/server/entry_collections/entry_collections.py # optimade/server/routers/utils.py # providers # requirements.txt
7e359be
to
250d0fd
Compare
Codecov Report
@@ Coverage Diff @@
## master #1562 +/- ##
==========================================
+ Coverage 91.09% 91.12% +0.02%
==========================================
Files 74 74
Lines 4538 4541 +3
==========================================
+ Hits 4134 4138 +4
+ Misses 404 403 -1
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. |
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 @JPBergsma, couple of minor comments but I'll approve and you can do as you wish
openapi/openapi.json
Outdated
@@ -3645,8 +3645,8 @@ | |||
"description": "Cartesian positions of each site in the structure.\nA site is usually used to describe positions of atoms; what atoms can be encountered at a given site is conveyed by the `species_at_sites` property, and the species themselves are described in the `species` property.\n\n- **Type**: list of list of floats\n\n- **Requirements/Conventions**:\n - **Support**: SHOULD be supported by all implementations, i.e., SHOULD NOT be `null`.\n - **Query**: Support for queries on this property is OPTIONAL.\n If supported, filters MAY support only a subset of comparison operators.\n - It MUST be a list of length equal to the number of sites in the structure, where every element is a list of the three Cartesian coordinates of a site expressed as float values in the unit angstrom (\u00c5).\n - An entry MAY have multiple sites at the same Cartesian position (for a relevant use of this, see e.g., the property `assemblies`).\n\n- **Examples**:\n - `[[0,0,0],[0,0,2]]` indicates a structure with two sites, one sitting at the origin and one along the (positive) *z*-axis, 2 \u00c5 away from the origin.", | |||
"nullable": true, | |||
"x-optimade-queryable": "optional", | |||
"x-optimade-support": "should", | |||
"x-optimade-unit": "\u00c5" | |||
"x-optimade-unit": "\u00c5", |
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'm really confused about what order this thing keeps changing it to (see #1429)... all the other changes are fine as they are alphabetical but this one seems to be the opposite.
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.
Okay I think the issue is actually with the release workflow, which keeps changing it back: 01101a4
Co-authored-by: Matthew Evans <[email protected]>
Several small changes I came across over the past months.
The most important one is to increase the sleep time for the elastic search container, as it takes more than 10 seconds to start on my laptop.