new option: weasyprint_log_path#100
Open
michalfapso wants to merge 1 commit intodomWalters:developfrom
Open
Conversation
d158034 to
8c4d92a
Compare
8c4d92a to
e5de977
Compare
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.
For setting an output path for the weasyprint log for easier debugging of weasyprint issues.
Although there was already the following code in plugin.py:
If I understand it correctly, this is supposed to show the weasyprint log in the mkdocs output when
verbose: true, but I don't see it there. That's why I made this new option for writing it to a separate file.