You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,11 +66,12 @@ The type generation process is recursive, traveling down through any nested `Inp
66
66
|`msg`|`string`| A plain, natural language description of the error. |
67
67
|`suberrors`|`<field-name>_Suberrors`| If your field has a complex type (eg. `InputObjectType` or `ListOfType`), then a `suberrors` field will be added with its own custom, generated type. |
68
68
69
-
The top-level `<field-name>ResultType` will have an additional field:
69
+
The top-level `<field-name>ResultType` will have a few additional fields:
|`valid`|`bool`| Resolves to `true` if all `args` and nested `fields` pass validation, `false` if not. |
74
+
|`result`|`mixed`| This is the original `type` you provided when declaring your field. Eg, If you specified `type` to be a `Book`, then the type of `result` will be `Book`. |
74
75
75
76
You can then simply query for these fields along with `result`:
0 commit comments