Correct typing of TaskDoc.transformations field #937
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.
Objects stored in TaskDoc.transformations can be serialized at init (for example,
pymatgen.alchemy.materials.TransformedStructure
), which leads to pydantic typing errors. This happens in atomate2 when output references are resolved, see discussion in atomate2 PR #623.This PR allows the typing of
TaskDoc.transformations
to beAny
, and adds tests for the new behavior.This would close atomate2 issue #607.