Support an enhanced Marpit enable state #64
Merged
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
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.
Marp Core should support an enhanced Marpit enable state, provided by Marpit v0.7.0.
StateCore.marpit(false)in core rule can disable Marp features together with Marpit now.We also added a trick to track enable state to decide whether rendering extended mark up in the renderer added by Marp Core. When Marpit state is disabled, we should render as if not using Marpit and Marp Core.
In addition, a few tokens have prefixed
marp_to prevent the collision between other plugins.We're working this to support switching Markdown preview and Marp slide deck preview in planned Marp VSCode plugin. (yhatt/marp#118)