-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add regression tests for both field and fragment arguments in relay r…
…esolvers Summary: ## Context When compiling relay resolvers we are missing validation on undefined global variables within resolvers. The global variables can be passed via resolver field or fragment arguments. We want to add a suite of regression tests for the following cases: - Relay resolver yields a scalar field without an associated fragment e.g. live or derived resolvers - Relay resolver yields a scalar field with an associated fragment - Passing both field and fragment arguments - Fragment args only - Field args only - Multiple undefined global variables - Linked field aka client edges ## This diff Adds the sad path version of this test: https://fburl.com/code/qal5u86k - Relay resolver yields a scalar field without an associated fragment e.g. live or derived resolvers - **Relay resolver yields a scalar field with an associated fragment** - **Passing both field and fragment arguments** - Fragment args only - Field args only - Multiple undefined global variables - Linked field aka client edges Add additional tests for relay resolvers to detect proper validation of their field and fragment arguments, which could be undefined Reviewed By: captbaritone Differential Revision: D50615537 fbshipit-source-id: 05b569d736419f4a71ce8656c7179d22420bafe4
- Loading branch information
1 parent
660f51f
commit 41a33a1
Showing
3 changed files
with
63 additions
and
1 deletion.
There are no files selected for viewing
32 changes: 32 additions & 0 deletions
32
...artifacts/fixtures/relay-resolver-with-undefined-field-and-fragment-args.invalid.expected
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
==================================== INPUT ==================================== | ||
# expected-to-throw | ||
|
||
query relayResolverWithUndefinedFieldAndFragmentArgsQuery { | ||
node(id: "SOME_ID") { | ||
...relayResolverWithUndefinedFieldAndFragmentArgs_user | ||
} | ||
} | ||
|
||
fragment relayResolverWithUndefinedFieldAndFragmentArgs_user on User { | ||
pop_star_name(field_arg: $undefined_field_arg, includeName: $undefined_fragment_arg) | ||
} | ||
|
||
fragment relayResolverWithUndefinedFieldAndFragmentArgsFragment_name on User | ||
@argumentDefinitions(includeName: {type: "Boolean!"}) { | ||
__typename | ||
name @include(if: $includeName) | ||
} | ||
|
||
# %extensions% | ||
|
||
extend type User { | ||
pop_star_name(field_arg: Int, includeName: Boolean!): String @relay_resolver(fragment_name: "relayResolverWithUndefinedFieldAndFragmentArgsFragment_name", import_path: "PopStarNameResolver") | ||
} | ||
==================================== ERROR ==================================== | ||
✖︎ Operation 'relayResolverWithUndefinedFieldAndFragmentArgsQuery' references undefined variable: '$undefined_fragment_arg'. | ||
|
||
relay-resolver-with-undefined-field-and-fragment-args.invalid.graphql:10:63 | ||
9 │ fragment relayResolverWithUndefinedFieldAndFragmentArgs_user on User { | ||
10 │ pop_star_name(field_arg: $undefined_field_arg, includeName: $undefined_fragment_arg) | ||
│ ^^^^^^^^^^^^^^^^^^^^^^^ | ||
11 │ } |
23 changes: 23 additions & 0 deletions
23
..._artifacts/fixtures/relay-resolver-with-undefined-field-and-fragment-args.invalid.graphql
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# expected-to-throw | ||
|
||
query relayResolverWithUndefinedFieldAndFragmentArgsQuery { | ||
node(id: "SOME_ID") { | ||
...relayResolverWithUndefinedFieldAndFragmentArgs_user | ||
} | ||
} | ||
|
||
fragment relayResolverWithUndefinedFieldAndFragmentArgs_user on User { | ||
pop_star_name(field_arg: $undefined_field_arg, includeName: $undefined_fragment_arg) | ||
} | ||
|
||
fragment relayResolverWithUndefinedFieldAndFragmentArgsFragment_name on User | ||
@argumentDefinitions(includeName: {type: "Boolean!"}) { | ||
__typename | ||
name @include(if: $includeName) | ||
} | ||
|
||
# %extensions% | ||
|
||
extend type User { | ||
pop_star_name(field_arg: Int, includeName: Boolean!): String @relay_resolver(fragment_name: "relayResolverWithUndefinedFieldAndFragmentArgsFragment_name", import_path: "PopStarNameResolver") | ||
} |
This file contains 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