We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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 text was updated successfully, but these errors were encountered:
The fix proposed to this issue in #561 is part of my fork which is also published to npm, with automatic updates enabled:
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
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.The text was updated successfully, but these errors were encountered: