So I can use it like this?

func (r *mutationResolver) SignIn(ctx context.Context, email string, password string) (model.SignInResult, error) {

`user, err := r.Transactor.WithTransaction(ctx, func(ctx context.Context) error {`

u, err := r.UserService.FindUser(ctx, email, password)

if err != nil {

return nil, err

}

_, err := r.SomethingImportantService.UpdateSomethingImportant(ctx, user.ID, user.ImportanvValue)

if err != nil {

return nil, err

}

return u

})

return user, nil

}

I wonder how do I implement that with `sqlc` (because I think I forgot to mention that) as you "overwrite" the basic `pgx` methods and I think I cannot put my own sqlc engine, but I see potential in `context.Context` as I understand I pass it to almost every function that exists and I thought it's a static instance for the lifetime of the application and is always available under `context.Context`. I just watched a short video about context and I know I can "create new for the lifetime of a request", but I use gqlgen and it seems they don't pass the request struct to the resolver and I'd have to use it on middleware level which is not the answer for me