Fix FrontMatter integration
#162
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
71 tasks
This was referenced Jul 4, 2024
mjbvz
approved these changes
Jul 8, 2024
Tyriar
approved these changes
Jul 8, 2024
chrmarti
approved these changes
Jul 8, 2024
This was referenced Aug 2, 2024
This was referenced Aug 5, 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.
brings the
FrontMatterrules into alignment with the markdown-it-front-matter package and VSCode's Markdown Preview featureprepares for the possible VSCode YAML TextMate grammar update old grammar => new grammar
the new grammar is more eager and breaks out of the current implementation
fixes: #164
fixes old VSCode issue: YAML frontmatter hyphens in markdown files have no scope applied
old:
new: