resolver return about domain-driven-hexagon

[Sairyss]

There is no need to throw HTTP exceptions in GrapnQL, it has it's own errors class:
import { GraphQLError } from 'graphql';
or
import { ApolloError } from 'apollo-server-express';
https://www.apollographql.com/docs/apollo-server/data/errors/

I would not do this in a resolver though, maybe in an exception filter https://docs.nestjs.com/exception-filters

Something like this:

@Catch(ExceptionBase)
export class GraphQLErrorFilter extends BaseExceptionFilter {
  override catch(exception: ExceptionBase, host: ArgumentsHost): void {
    if (host.getType<GqlContextType>() !== 'graphql') {
      return super.catch(exception, host);
    }

    const error = new ApolloError(exception.message, exception.code, {
      cause: exception.cause,
      correlationId: exception.correlationId,
      metadata: exception.metadata,
    });
    error.stack = exception.stack;

    throw error;
  }
}

This way domain errors will be transformed to GraphQL errors with a correct error code, no need for boilerplate matching

[yazid-emerm]

thanks for these explanation !

Indeed it's better !