Member Junction
    Preparing search index...
    • @NoLog — marks a resolver argument or input-type field as never-loggable.

      Two modes, distinguished by decorator arity at runtime:

      Parameter — applied to an @Arg(...) parameter on a resolver method:

      @Mutation(() => Boolean)
      async VoiceTestHubSpotCredential(
      @Arg('accessToken') @NoLog accessToken: string,
      @Ctx() ctx: AppContext,
      ): Promise<boolean> { ... }

      Property — applied to a @Field() on an @InputType class:

      @InputType()
      export class GetDataInputType {
      @Field(() => String) @NoLog Token: string;
      @Field(() => [String]) Queries: string[];
      }

      The variables-logging middleware reads these marks at runtime via hasNoLogParameter / getNoLogFields and replaces the marked value (or whole arg) with "<redacted>" before emitting the variables block. Metadata-covered fields (entity columns with EntityFieldInfo.Encrypt=true) do not need @NoLog — applying it is harmless but redundant. Use @NoLog for arguments that the redactor cannot identify via metadata: custom-resolver parameters, MCP tool args, fields on input types that don't map to a known entity.

      Parameters

      • target: object
      • OptionalpropertyKey: string | symbol
      • OptionalparameterIndex: number

      Returns void