Run Resolver after guards

[RubenFricke]

I have a guard on my routes which handle auth. Besides that, this auth add a user object to the request model:

request.user = {
....
}

I want to use this user data in my custom resolver so I know which user is logged in. This is the start of my custom resolver:

@Injectable()
export class MemberLanguageResolver implements I18nResolver {
  constructor(private readonly memberService: MemberService) {}

  async resolve(context: ExecutionContext): Promise<string | undefined> {
    const request = context.switchToHttp().getRequest();
    const user = request.user;
    console.log(user);

However, when adding console.log statements, I notice that the resolver runs after the guard, resulting in user being undefined. How can I change this so the resolver runs after the guard on my route.

Important to note, I've tried disableMiddleware: to be true and false. When I set it to true, the user object has been set (so it runs correctly, but whenever it should generate an error response it crashses:

TypeError: Cannot read properties of undefined (reading 'service')```

And when I set it to false, the error message gets correctly generated, but then the user object is undefined. 

Thanks in advance!