Incorrect __typename type
See original GitHub issueIn the following, __typename
should be possibly undefined
.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
__typename field prevents updates · Issue #1564 ... - GitHub
Hi, High-level issue: appended __typename field causes errors when updating. Details: When retrieving data for a custom address type, ...
Read more >How to remove __typename for a specific query - Help
Hello. I have the same problem, so actually it would be very helpful to strip typename from data. For example fetch it from...
Read more >Inconsistent Typename Error - Relay
The best way to fix this is to make your type spec compliant. For the case of 2 different types backed by the...
Read more >How to remove the `__typename` field from the graphql ...
If you're using a query results as initial state, you'll need to transform it first to strip out the __typename fields (and any...
Read more >Dealing with __typename and mutations : r/graphql - Reddit
I have some cases in my graphql apps where I. query an object. object has an array on it of object types (thus...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Tell me if i understood correctly, you want the
__typename
field to beType
instead ofType | undefined
when you are explicitly querying__typename
, is this right?Yeah