fix: use the Logger passed in RabbitMQModule config instead of default #663
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello, I discovered an issue when passing a custom Logger to the
RabbitMQModule
:Some logs are made using the logger passed in the config:
But some other logs, like ones written in
onApplicationBootstrap
, don't use the Logger provided in the config but thelogger
property of theRabbitMQModule
which is not configurable.So my fix consists of using the logger from the provided config everywhere in the
RabbitMQModule
.And now all logs are correct: