You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using the Argdown extension on VS Code, and it's generally working fine. However, if I try to add YAML data, especially frontmatter, to an Argdown file, problems arise. If I add any YAML data to a statement, or if I have more than one line of frontmatter, the tokenizer seems to think the entire document after the YAML data is also YAML. This causes the rest of the document to be incorrectly syntax-highlighted. It's not a functionality problem, and I can get around it if I don't include any YAML data, but it's nice to include more than one line of frontmatter without the rest of the document's coloring being thrown off.
I've included a picture of the syntax coloring and the debug view of the scope, showing that the rest of the Argdown is being interpreted as YAML. I'm using VS Code 1.94.2.
The text was updated successfully, but these errors were encountered:
I've been using the Argdown extension on VS Code, and it's generally working fine. However, if I try to add YAML data, especially frontmatter, to an Argdown file, problems arise. If I add any YAML data to a statement, or if I have more than one line of frontmatter, the tokenizer seems to think the entire document after the YAML data is also YAML. This causes the rest of the document to be incorrectly syntax-highlighted. It's not a functionality problem, and I can get around it if I don't include any YAML data, but it's nice to include more than one line of frontmatter without the rest of the document's coloring being thrown off.
I've included a picture of the syntax coloring and the debug view of the scope, showing that the rest of the Argdown is being interpreted as YAML. I'm using VS Code 1.94.2.

The text was updated successfully, but these errors were encountered: