Use aliases when handling response_fields #159
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #149.
Fixes #157.
When handling
response_fields
, the dictionary created from the entry pydantic model is created using aliases, i.e., the provider-specific prefix is added correctly toctime
(and future provider-specific fields).This ensures the resulting entries are correctly presented when
response_fields
is used.As a note, there are some optimizations that should be possible when Materials-Consortia/optimade-python-tools#560 has been merged and released.