Allow caller to specify pegdown extensions used #2
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
Currently the generator hard-codes all pegdown extensions to on. This is annoying as e.g. hard line breaks are a bad fit for documentation. This changes that to a default, and allows a caller to pass through a pegdown extension bit-mask integer to customise the extensions to their own taste.
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.
Currently the generator hard-codes all pegdown extensions to on. This is
annoying as e.g. hard line breaks are a bad fit for documentation.
This changes that to a default, and allows a caller to pass through a pegdown
extension bit-mask integer to customise the extensions to their own taste.
Any objections?