Open jbreckel opened 2 years ago
The currently used custom scalar types are all strings, as noted in the comments.
Using unknown instead of any would also be the type safe way as described here.
unknown
any
The fix proposed to this issue in #561 is part of my fork which is also published to npm, with automatic updates enabled:
The currently used custom scalar types are all strings, as noted in the comments.
Using
unknown
instead ofany
would also be the type safe way as described here.