Add variable filter tests - #8363
Closed
glen-84 wants to merge 9 commits into
Closed
Conversation
glen-84
marked this pull request as draft
June 16, 2025 13:17
Member
Author
|
Superseded by #10126, which fixes the underlying variable coercion bug for expression-based filter fields and carries the regression test. Drafted by Claude (Anthropic AI assistant). |
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
2 participants
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
latestItem, bound toItems.OrderByDescending(...).Take(1)), verifying the query executes without errors whether thewhereargument is supplied inline or through a GraphQL variable.Test plan
Without_Variables:whereprovided inline in the query, asserts no execution errors.With_Variables: the same filter provided via aCollectionFilterInput!variable, asserts no execution errors.