fix: handle MappedAsDataclass in create_update_dict - #1575
Open
pctablet505 wants to merge 2 commits into
Open
Conversation
pctablet505
marked this pull request as ready for review
July 27, 2026 10:37
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
1 participant
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 #1440
When a user model uses SQLAlchemy's
MappedAsDataclass, registering a user fails on optional fields becausecreate_update_dictdrops unset values that the dataclass__init__expects as keyword arguments.This keeps
exclude_unset=Truefor partial updates but passesexclude_unset=Falseduring user creation, so default values for optional fields are included.