Resolver context is not updated once a user is logged in about graphql-laravel HOT 2 CLOSED

I've no real idea yet, but you can try resolving the AuthManager in the resolve method and not inject it via constructor, does that change anything?

from graphql-laravel.

I'm closing this for two reasons:

• no feedback for a long time

• the context can be controlled by the user, but details are lacking how this is handled here (you can inject your own context and handle this from there)

  any subsequent resolver context

  I cannot confirm it with the current data, but I've a feeling it might be a Laravel internal "thing". Can you replicate this in a simple environment without graphql, e.g. a simple HTTP action where you mutate the authentication and subsequent call work correctly?

from graphql-laravel.