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
#### 5. Extra `__typename` present, or required `__typename` missing.
367
385
368
386
Experiment with the following configuration options to keep your codebase changes to a minimum:
369
387
370
-
***skipTypename**: prevents adding `__typename` to generated types unless explicitly in the selection set.
371
-
***skipTypeNameForRoot**: skips `__typename` specifically for root types (Query, Mutation, Subscription). Ignored if `__typename` is explicitly in the selection set
372
-
***nonOptionalTypename**: always adds `__typename` and makes it a required (non-optional) field.
373
-
***addTypenameToSelectionSets**: injects `__typename` directly into the generated document node selection sets.
374
-
***resolversNonOptionalTypename**: makes `__typename` non-optional in resolver mappings without affecting base types. Supports granular control via object form.
388
+
-**skipTypename**: prevents adding `__typename` to generated types unless explicitly in the
389
+
selection set.
390
+
-**skipTypeNameForRoot**: skips `__typename` specifically for root types (Query, Mutation,
391
+
Subscription). Ignored if `__typename` is explicitly in the selection set
392
+
-**nonOptionalTypename**: always adds `__typename` and makes it a required (non-optional) field.
393
+
-**addTypenameToSelectionSets**: injects `__typename` directly into the generated document node
394
+
selection sets.
395
+
-**resolversNonOptionalTypename**: makes `__typename` non-optional in resolver mappings without
396
+
affecting base types. Supports granular control via object form.
0 commit comments