Repository navigation
Fix metadata validation when reusing values across fields - #76
Merged
Merged
Conversation
dschwartznyc
approved these changes
Nov 12, 2026
4 tasks done
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
Reusing an object in a reference-capable field could initialize empty
@refmetadata slots on that object. Subsequent validation in a field without reference permissions then rejected those slots, even though their values wereNone.Validate only populated metadata against the receiving field's permissions. Preserve existing slots so later reference assignments continue to work. Forbidden non-None values remain rejected, including
False,0, and empty strings.Broader ownership and copying behavior remains tracked in #66 and #49.
Validation
git diff --checkpassed.Fixes #15.