-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding newline in between frontmatter delimiters causes issues #10
Comments
Not reproducible on the demo here: https://wooorm.com/markdown-tm-language/. I also don’t see it locally in VS Code with MDX. Perhaps report this to the YAML grammar you use with VS Code. Looks like they mess up when there’s a |
/cc @remcohaszing who knows more about yaml and vs code than me :) |
Interesting 🤔 I am unable to reproduce this in my own VSCode setup. However, I am able to reproduce this with all extensions disabled. Installing the YAML extension resolves it. This means it’s a bug with the builtin VSCode YAML grammar. The YAML extension uses its own grammar which isn’t broken. Both VSCode and the YAML extension pull the YAML grammar from external sources, but not the same source. So really this is an issue with the external YAML grammar that VSCode uses. TL;DR: It’s an issue in VSCode (microsoft/vscode#224862). As a workaround, install the YAML extension. It’s really good, you should use it anyway. :) |
How bizarre! Installing the YAML extension did solve the issue, thank you. |
Also had this issue and the YAML extension resolved it! Cheers! |
Hi! Title says it all but when I try adding... any kind of newline in between the frontmatter delimiters (
---
), the syntax highlighting goes hay wire. I'm coming from MDX's VS Code extension. I've turned off all extensions except for MDX's and my theme.Without frontmatter:
With frontmatter, but empty:
With frontmatter and a newline:
With frontmatter and actual values:
Still occurs when I turn my theme off as well:
Please let me know how I can help. Thank you!
The text was updated successfully, but these errors were encountered: