From 4d93de6a9e1bec725d10dcb320d110a66ecc0e5e Mon Sep 17 00:00:00 2001 From: Niels Mokkenstorm Date: Sun, 17 May 2026 11:41:19 +0200 Subject: [PATCH] fix(async-job): re-export AsyncJobModule from AsyncJobGraphQLModule (again) (#34) --- .../modules/async-job/async-job-graphql.module.ts | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/apps/api/src/modules/async-job/async-job-graphql.module.ts b/apps/api/src/modules/async-job/async-job-graphql.module.ts index 3a9637a..b942395 100644 --- a/apps/api/src/modules/async-job/async-job-graphql.module.ts +++ b/apps/api/src/modules/async-job/async-job-graphql.module.ts @@ -4,17 +4,15 @@ import { AsyncJobResolver } from "./async-job.resolver"; import { TypedAsyncJobInterceptor } from "./typed-async-job.interceptor"; /** - * GraphQL surface for AsyncJob. The data layer (entity, mapper, policy, - * service) lives in `@cv/core` as `AsyncJobModule`; this module is the - * api-only wiring for the `asyncJob` query and the bundle interceptor. - * - * Consumers needing the data layer (e.g. resolvers using the bundle in - * other feature modules) should import both this module (for the - * interceptor) AND `AsyncJobModule` from `@cv/core` directly. + * GraphQL surface for AsyncJob. The data layer (`AsyncJobModule` in + * `@cv/core`) is re-exported because `TypedAsyncJobInterceptor`'s + * `AsyncJobService` dep is resolved in the consumer's module scope, not + * here — without the re-export every feature module using the bundle has + * to import both modules explicitly. */ @Module({ imports: [AsyncJobModule], providers: [AsyncJobResolver, TypedAsyncJobInterceptor], - exports: [TypedAsyncJobInterceptor], + exports: [TypedAsyncJobInterceptor, AsyncJobModule], }) export class AsyncJobGraphQLModule {} -- 2.51.2