Replies: 1 comment
-
|
Unfortunately this is the only way to handle custom scalars since the codegen plugin does not have a way of knowing what to map it to otherwise. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When using client code generation from a schema with a lot of scalers the typeMapping option gets very cumbersome. Here is an example mapping a large amount of Gitlab GraphQL Id fields. Gitlab resources all have a scaler Id of a custom type. For example
User.Idis typeUserIdwhich is really just a string that looks something likegib://Users/{number}. Mapping that to a string is fine for my use case.To get code generation working on all these, I need:
Am I missing something, is there a more automatic way of doing this?
Beta Was this translation helpful? Give feedback.
All reactions