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
I spent some time on studying on how to migrate from apollo to graphql-codegen seamlessly. Unfortunately graphql-codegen does not provide no-brainer way to migrate. It is possible to mimic the behavior of generating multiple files next to the source file in __generated__/[OperationName].ts. However, The [OperationName_Type_fieldName] naming convention cannot be achieved. Therefore, migration requires us to adopt the convention of graphql-codegen, which requires significant code change on how our hand-written code interacts with the generated code.
The text was updated successfully, but these errors were encountered:
I spent some time on studying on how to migrate from apollo to graphql-codegen seamlessly. Unfortunately graphql-codegen does not provide no-brainer way to migrate. It is possible to mimic the behavior of generating multiple files next to the source file in
__generated__/[OperationName].ts
. However, The[OperationName_Type_fieldName]
naming convention cannot be achieved. Therefore, migration requires us to adopt the convention of graphql-codegen, which requires significant code change on how our hand-written code interacts with the generated code.The text was updated successfully, but these errors were encountered: