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
As mentioned in #123 it could help users avoid cache bugs and copy/pasting id throughout all their queries if it was added automatically to fields that don't specify it, just like how __typename is. No error is reported when a user doesn't add id yet their cache will fail to update, which can be unexpected behavior
It's a habit to add it to all fields for people that have been working with graphql for a while, but it's not immediately obvious to new graphql users. It would shrink queries and make it more apparent what fields the widget is actually using
The text was updated successfully, but these errors were encountered:
As mentioned in #123 it could help users avoid cache bugs and copy/pasting
id
throughout all their queries if it was added automatically to fields that don't specify it, just like how __typename is. No error is reported when a user doesn't addid
yet their cache will fail to update, which can be unexpected behaviorIt's a habit to add it to all fields for people that have been working with graphql for a while, but it's not immediately obvious to new graphql users. It would shrink queries and make it more apparent what fields the widget is actually using
The text was updated successfully, but these errors were encountered: