feat: new and guard

[jmcdo29]

With the newAndGuard, devs can now set up cases where they want to use an OrGuard to handle an (A && B) || C kind of condition, or any other complex logical approach they'd like. Devs are also now able to correctly pass injection tokens to the AndGuard and OrGuard and use custom providers for their guards that are registered as providers

[changeset-bot]

🦋 Changeset detected

Latest commit: bc9bbdf

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@nest-lab/or-guard	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[its-monotype]

@jmcdo29 Wow, I'm so hyped. I hope I correctly get it that now I can replace this cumbersome solution I had to implement:

import { CanActivate, ExecutionContext, Injectable } from '@nestjs/common';

import { JwtAuthGuard } from '@/auth/guards/jwt-auth.guard';
import { RolesGuard } from '@/auth/guards/roles.guard';

@Injectable()
export class JwtAuthRolesCompositeGuard implements CanActivate {
  constructor(
    private jwtAuthGuard: JwtAuthGuard,
    private rolesGuard: RolesGuard,
  ) {}

  async canActivate(context: ExecutionContext): Promise<boolean> {
    const hasJwtAuthAccess = await this.jwtAuthGuard.canActivate(context);
    const hasRolesAccess = await this.rolesGuard.canActivate(context);

    if (hasJwtAuthAccess && hasRolesAccess) {
      return true;
    }

    return false;
  }
}

with this neat... smth like Or(AndGuard(JwtAuthGuard, RolesGuard), ApiKeyGuard), right? That's what was I looking for!

Thanks for your work, it's super handy! 😃

[jmcdo29]

@its-monotype Yes, that's correct. And yes, you still need to add the guards to the providers array so the ModuleRef can grab them dynamically