fix: coerce nested BaseModel fields - #295
Merged
jbeckwith-oai merged 4 commits intoAug 11, 2026
Merged
Conversation
Store coerced nested model values during BaseModel construction and assignment instead of preserving raw hashes. Add coverage for nested model fields and arrays.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 110b3660c9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
HAYDEN-OAI
approved these changes
Aug 10, 2026
HAYDEN-OAI
left a comment
Contributor
There was a problem hiding this comment.
Reviewed the nested model coercion changes, including collection error aggregation, union isolation, identity preservation, and the follow-up nullable collection fix. No substantive issues found.
Open
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.
Summary
Fixes nested
BaseModelcoercion so generated setters store successfully coerced model values instead of preserving raw hashes and arrays.Root cause
The generated setter assigned the return value of
Hash#storetoerror. BecauseHash#storereturns the value it stores, the successful branch that storedcoercedwas unreachable.Composite converters also shared one mutable error slot. A later successful field or collection item could clear an earlier error, while a rejected union variant could overwrite the error state of the selected variant.
Changes
BaseModelcoercion.Before / after
Before this fix, the generated setter returned raw hashes:
After this fix, successful coercion is stored:
Validation
./scripts/test— 437 runs, 1,359 assertions, 0 failures./scripts/lint— RuboCop, Sorbet, and Steep all pass