Allow for user customizable renderer scripts #9
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
also ensure it's reset to null if tests are run out of order
mallardduck
changed the title
|
Thanks! Lost track of this one |
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.
Per the title this PR allows a user to set a customizable renderer script. This can be helpful if someone wants to further control how Shiki renders a block to HTML. In my case the use-case I'm hoping to support is the same one used in the tests. Modifying the output to include CSS properties/variables.
It's accomplished simply by allowing the Process CWD path to be customized. This way someone can easily copy the existing renderer script and make any needed modifications. Then they just call the static method somewhere before using the Shiki class to render a code block.