Skip to content

Commit 0ba871e

Browse files
Merge pull request #1332 from jmcdo29/logger-warning
docs(logger): adds back warning of custom logger
2 parents e9cb53a + ba8f14c commit 0ba871e

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

content/techniques/logger.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -135,6 +135,8 @@ Here we use the `get()` method on the `NestApplication` instance to retrieve the
135135

136136
You can also inject this `MyLogger` provider in your feature classes, thus ensuring consistent logging behavior across both Nest system logging and application logging. See <a href="techniques/logger#using-the-logger-for-application-logging">Using the logger for application logging</a> below for more information.
137137

138+
The only downside of this solution is that your first initialization messages won't be handled by your logger instance, though, it shouldn't really matter at this point.
139+
138140
#### Using the logger for application logging
139141

140142
We can combine several of the techniques above to provide consistent behavior and formatting across both Nest system logging and our own application event/message logging. In this section, we'll achieve this with the following steps:

0 commit comments

Comments
 (0)