Philip Scott

Isn't doing auth through the GraphQL layer impossible in certain cases? (e.g. cookie-based authentication) https://github.com/99designs/gqlgen/blob/master/docs/content/recipes/authentication.md > Because GraphQL is transport agnostic we can't assume there will even be an HTTP...

I suppose, but the question is whether it's even possible for some users. Suppose you're sending an authorization token through a cookie, how will you be able to access it...

Can't you just create a wrapper interface and struct? ```go package wrapper type Querier interface { db.Querier WithTx(tx *sqlx.Tx) Querier } type Queries struct { *db.Queries } func (q *Queries)...

To make matters more complicated, some web servers like NGINX have default timeouts that are reliant on PINGs/PONGs [1]: > By default, the connection will be closed if the proxied...

This is honestly the most well-structured issue I have ever seen.

Please edit your message such that it complies with the Bug Report template: I can't really help you if you don't provide steps to reproduce :smiley:

I'm kinda low on bandwidth at the moment; it's currently exam season for me. I might be able to fix the bug after this weekend. This particular issue is caused...

Not at the moment. I recommend you look at the source code here and just tweak it to your liking (functions are less than 30 lines): https://github.com/ScottyFillups/ffprobe-client/blob/master/index.js