fix(graphql-relational-transformer): filter key fields from authFilter in relational resolvers #3383
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
Details
When owner or other auth fields are part of the composite primary key, they're already used in the key condition expression. DynamoDB prohibits using primary key attributes in filter expressions, causing the error:
"Filter Expression can only contain non-primary key attributes"
This fix filters out any authFilter fields that overlap with the key condition fields (references) before adding them to the filter expression.
Test plan
Closes #3364
🤖 Generated with Claude Code