Conversation
Contributor
|
Anything wrong with I find this easier to configure as the name maps to the module import path.
|
|
That’s definitely the recommended way for applications. For libraries it’s a bit different: you may want your logical model/layout of modules to be different than your physical model/layout. E.g. you probably don’t want logs coming for a private module. |
…into fan-logger-names
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request improves our logging behaviour by fanning out different logger names...
code:
console:
(output prior to this change)...
This allows better control of logging, and also reads more clearly to me.
(parameters passed to the "trace" extension are unaffected by this change.)
TODO