Works fine when I use NestFactory.create but when instantiated via Test.createTestingModule it does not
#why does logger not work in test module
crude oriole
ashen pilot
The default test logger is set to error only. You can modify this as needed. I think with modRef.useLogger? Haven't had to mess with that for a while'
unique gazelle
setLogger
setLogger
useMocker
man 😅
I guess I'll propose changing setLogger to useLogger for v11 😎
stray fulcrum
Btw it's that way so it does not pollute your unit test log. I all goes well, you ideally just want a green PASS, instead of half a page of logs between each test.
ashen pilot
I guess I'll propose changing `setLogger` to `useLogger` for v11 😎
Why not v10?
unique gazelle
Why not v10?
we would mark that api as deprecated while introducing the new one in v10
ashen pilot
we would mark that api as deprecated while introducing the new one in v10
That's what I would be hoping for
unique gazelle
Btw it's that way so it does not pollute your unit test log. I all goes well, yo...
yeah, we could mention this in the docs
stray fulcrum
By the way, as the method naming goes, I think it's alright. The useXx is used within the test module builder, that is, before .compile is called. This is pretty much a convention with the builder pattern. (That, and withXx)
The setXx, on the other hand, is used to set something on an already created object.
unique gazelle
By the way, as the method naming goes, I think it's alright. The `useXx` is used...
oh, indeed
never used that before
a bit confusing to me tho
stray fulcrum
Oh wait, it's the other way around??? 🤔
unique gazelle
useLogger came from NestApplicationContext
setLogger came from TestingModuleBuilder