I have changed the ApplySyntaxHighlighting so that Markdig no longer … #13
Conversation
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
…innapropriately does not apply a <pre> blog to names not known to the ColorCode project. I also made it optional so users can opt out of not getting the expected results of a ``` block rendering in a <pre> tag"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
…innapropriately does not apply a <pre> block to language names not known to the ColorCode project. I also made it optional so users can opt out of not getting the expected results of a ``` block rendering in a <pre> tag"
note some of the properties may need to change back from public string Id => "default"; to public string Id { {get return "default"; } } or similar...
This is kind of a hack as I believe markdig does not handle ```unknownlang correctly as it renders the text in a ``` section as <div and not <pre. This hack simply fixes that.