Add control over mounting debug message on application startup

[wilfreud]

There is this message on startup " DEBUG [ClsModule] Mounting ClsMiddleware to *", even in production.
It just bothers me

[Papooch]

I've been thinking about adding a bunch of other logs for debugging, akin to nestjs/nest#7910. This issue could be implemented together with it.

[wilfreud]

That sounds good. plus adding some sort of control over those logs would be good. That was the main point of me issue, I just realized I forgot to mention on.

[Papooch]

I'm thinking of these possible options:

• CLS_DEBUG=true - enables only debug logs from this library
• NEST_DEBUG=true - enables debug logs for Nest and this library
• NEST_DEBUG=true - enables only debug logs for Nest + NEST_DEBUG=nestjs-cls - enables debug logs for Nest and this library
• DEBUG=nestjs-cls - enables only debug logs from this library, possibly in combination with other libraries that also use the DEBUG env var (DEBUG=express,nestjs-cls)

[wilfreud]

Sounds good.

I was thinking more of a programatical to do it, like passing an object in the forRoot method.

ClsModule.forRoot({
      global: true,
      middleware: { mount: true },
}),

But I think doing both could be great, providing two ways of doing it. Though there would be a need to define precedence between envs & config object.

PS: why the NEST_DEBUG for control over NestJS logs themselves ? (I feel like I'm missing something)

[Papooch]

why the NEST_DEBUG for control over NestJS logs themselves

NEST_DEBUG already controls NestJS's own debug logs when it is set to any value. I was thinking I could use the same variable to also enable debug logs of nestjs-cls

[Papooch]

Added in https://github.com/Papooch/nestjs-cls/releases/tag/nestjs-cls%406.2.0