make easier for developers to produce alternate HTML for specific events/tags#629
Closed
ultrasaurus wants to merge 2 commits into
Closed
make easier for developers to produce alternate HTML for specific events/tags#629ultrasaurus wants to merge 2 commits into
ultrasaurus wants to merge 2 commits into
Conversation
example of writing alt html for one tag, plus fixes fixed warnings made some fields and functions public for usability
Collaborator
|
This can be used as inspiration for a full-featured external crate for the HTML rendering, but is out of scope in pulldown-cmark. |
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
2 participants
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 a possible approach to addressing #584
It could also allow for developers to experiment with CommonMark extension that conform to standard syntax.
It involves making
HTMLWriterpublic and refactoring to create a publicrender_eventfunction. I'm curious if the project maintainers see this as something that the library could support, and if so, whether this approach is reasonable.Happy to work on it further, with feedback. Or please let me know if this is not something you ever want to pursue, in which case, I'll consider a different library or possibly maintain my own fork for my use case.