Automatically create underlying SLF4J logger with name autodetection #32
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 is solution of some issues described here: #28
Subclassing from Logging trait can make impossible to configure logging level for some classes, and writing long string like this:
can be tedious.
With this patch underlying logger name can be detected automatically via macros. All you need to do is:
It finds nearest encircling class and uses its name for creating underlying logger.