We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently if you want to describe a provider field in the relevant /info/<endpoint> endpoint, you have to add it explicitly to a pydantic model.
/info/<endpoint>
Instead of a simple list of provider fields like provider_fields = {"structures": ["volume", "band_gap"], we should also allow something like
provider_fields = {"structures": ["volume", "band_gap"]
provider_fields = { "structures": [ {"name": "volume", "description": "The cell volume", "units": "A^3"}, {"name": "band_gap", "description": "The band gap", "units": "eV"} ] }
s.t. the description/units etc. can be propagated to the relevant info endpoint.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Currently if you want to describe a provider field in the relevant
/info/<endpoint>
endpoint, you have to add it explicitly to a pydantic model.Instead of a simple list of provider fields like
provider_fields = {"structures": ["volume", "band_gap"]
, we should also allow something likes.t. the description/units etc. can be propagated to the relevant info endpoint.
The text was updated successfully, but these errors were encountered: