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
Which just means diffs will grow and the function signature will change as new fields are added. Seems like if a struct was generated for the args, the signature would be stable and there would be less to review in diffs.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Note: I am not a golang developer, so please excuse me if I use the wrong names.
We are migrating from an existing graphql server, written using
@graphql-codegen
. One of the things that does, is if we have things defined likeIt generates interfaces rolling up those things together, ie:
But, I can see gqlgen just adds all the args to the generated query / mutation function:
Which just means diffs will grow and the function signature will change as new fields are added. Seems like if a struct was generated for the args, the signature would be stable and there would be less to review in diffs.
Beta Was this translation helpful? Give feedback.
All reactions