Add logging support for converters #801
Merged
Conversation
This file contains 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
robertpanzer
force-pushed
the
converter-logging
branch
from
3fb94ef
to
87ef7b1
Compare
|
LGTM |
|
Awesome, thanks! It corresponds mostly to what you proposed on gitter. |
|
I'll try to do a new RC with this. |
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 PR is a proposal for adding logging support for converters.
If a converter implements the interface
org.asciidoctor.log.Logging, then Asciidoctor will set aorg.asciidoctor.log.LogHandlerviaLogging.setLogHandler(logHandler)after the converter was created.The AbstractConverter already implements this interface and provides the method
log(LogRecord)to log.