I enabled tracing on my gqlgen server which had a Subscription added to it. After doing so I immediately hit https://github.com/99designs/gqlgen-contrib/issues/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).
I would expect that StartOperationParsing would still be called in subscriptions (since request parsing, etc. still happens).
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 is still an issue, so it shouldn't be marked stale
We have a big change in #885 .
I think this issue will be fixed in master / HEAD.
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.
Most helpful comment
We have a big change in #885 .
I think this issue will be fixed in master / HEAD.