Improve Pydantic model usage#744
Merged
superstar54 merged 1 commit intoaiidateam:mainfrom Jan 22, 2026
Merged
Conversation
45fabc6 to
c418118
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix #741
Previously, Pydantic Models or dataclasses were annotation-only, and users still needed to provide plain dict as inputs/outputs.
On top of scinode/node-graph#142 and aiidateam/aiida-pythonjob#66, this PR allows users to use a Pydantic model as both input and output. No need to provide plain dict.