fix: auto-exclude relator fields from attributes#114
Merged
Conversation
When a Relator is defined for a field, that field is now automatically excluded from serialized attributes under the default projection (null). Previously the field appeared in both attributes and relationships, which is incorrect per the JSON:API spec. Closes #77 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
fa0b5e0 to
e1ae5d7
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.
Summary
When a
Relatoris defined for a field, that field is now automatically excluded from serializedattributesunder the defaultprojection: null. Previously the field appeared in bothattributesandrelationships, which is incorrect per the JSON:API spec. Users had to explicitly set a projection to work around this.Test plan
test/issue-77.test.ts)Closes #77
🤖 Generated with Claude Code