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
"actually, I’ll just write it down here: it’s in execute.js, all the way at the end in getFieldDef. I think we should just return a default id field if it doesn’t exist on the type. That’s also where the __typename stuff gets handled."
Just something to note when we add the functionality to add id and typename to all queries.
The text was updated successfully, but these errors were encountered:
After talking with @martijnwalraven, we decided this is probably not a good idea for now, and we should load type information on the client if we want to get IDs.
Alternatively, we could convince the GraphQL team to add IDs to the spec.
From @helfer:
"actually, I’ll just write it down here: it’s in execute.js, all the way at the end in getFieldDef. I think we should just return a default id field if it doesn’t exist on the type. That’s also where the __typename stuff gets handled."
Just something to note when we add the functionality to add
id
andtypename
to all queries.The text was updated successfully, but these errors were encountered: