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
While the graphql queries differ, the "return" type is the same. It would be convenient if they could both be the same type in genqlient, rather than two different types with identical shapes.
Good idea! This would need to be opt-in, I think, since it does make those types less stable (if you change one of the queries, say). But #12 is naturally opt-in, so it would make a lot of sense for them to go together.
Ah, another option for how to do this would be via fragments; if you define a shared fragment, and spread that into all the queries, then genqlient can notice that and share the type. This is natural because then the queries actually guarantee that the types match. But of course it depends on #8.
We have two different gql queries:
While the graphql queries differ, the "return" type is the same. It would be convenient if they could both be the same type in genqlient, rather than two different types with identical shapes.
This is probably related to #12.
The text was updated successfully, but these errors were encountered: