Update the id for scoping bespoke template styles #516
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
This was referenced Jul 17, 2024
This was referenced Aug 6, 2024
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.
For making smaller the output HTML, we had used ID
pto scope styles forbespoketemplate interfaces. When Marp Core v3.6.0 is coming to Marp CLI, it may conflict with user-generated anchor by Markdown headings just like# p.Thus, we've changed the anchor for the whole of HTML document from
pto:$p. Both of:and$are not using as a character of the slug anchor by the default slugifier in Marp Core v3.6.0 so the interface ofbespoketemplate will become safe from user-generated anchors.