-
Notifications
You must be signed in to change notification settings - Fork 1.2k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
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
Allow returning errors when marshaling scalars #743
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is still valid. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still valid. @vektah if you agree, I can create a PR with this change during my spare time. It would be a breaking change, but I can try to avoid this. Waiting for your feedback. Cheers! |
Implementing this would make resolving issue #1195 simpler. |
Linking #1645 because it also deals with changing the scalar interface. |
This can probably be closed. #1652; using the context interface allows returning an error. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I have a case when marshaling a scalar can return an error.
Currently we have the following
Marshaler
andUnmarshaler
interfaces:It'd be great to allow return errors for
Marshaler
, similarly toUnmarshaler
.versions
gqlgen version
0.9.0The text was updated successfully, but these errors were encountered: