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 enabled tracing on my gqlgen server which had a Subscription added to it. After doing so I immediately hit 99designs/gqlgen-contrib#10 -- which stems from the fact that StartOperationParsing is never called for Subscription calls. It seems that the websocket handler has its own query parsing (separate from the the on in graphql.go which starts the trace).
What did you expect?
I would expect that StartOperationParsing would still be called in subscriptions (since request parsing, etc. still happens).
The text was updated successfully, but these errors were encountered:
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 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.
What happened?
I enabled tracing on my gqlgen server which had a Subscription added to it. After doing so I immediately hit 99designs/gqlgen-contrib#10 -- which stems from the fact that
StartOperationParsing
is never called for Subscription calls. It seems that the websocket handler has its own query parsing (separate from the the on in graphql.go which starts the trace).What did you expect?
I would expect that
StartOperationParsing
would still be called in subscriptions (since request parsing, etc. still happens).The text was updated successfully, but these errors were encountered: