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
{{ message }}
This repository has been archived by the owner on Mar 21, 2024. It is now read-only.
The reason-markdown-codeblock.json syntax injects Reason syntax highlighting into Markdown ``` fences with a language ID of re, reason, or reasonml. Or, at least, that's what it's supposed to do. In reality, any match of the pattern (re|reason|reasonml)(\s+[^`~]*)?$ in an unhighlighted Markdown code block will assign the highlighting of the rest of the code block to Reason. The problem is with the start pattern for the syntax injection, at .repository.reason-code-block.begin.
I've encountered this intermittently over a couple of years, but as I recently wrote a language extension for VS Code, I fired up “Developer: Inspect Editor Tokens and Scopes” and quickly found the issue. See how the scope changes to meta.embedded.block.reason after writing re earlier in the code block. (Although my theme is Adapta Nocto, I tested that it has the same behavior with the default.)
I'm aware of this extension's deprecation and expect nothing to come of this, but I figured I'd report it, since I had already triaged it.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The reason-markdown-codeblock.json syntax injects Reason syntax highlighting into Markdown
```
fences with a language ID ofre
,reason
, orreasonml
. Or, at least, that's what it's supposed to do. In reality, any match of the pattern(re|reason|reasonml)(\s+[^`~]*)?$
in an unhighlighted Markdown code block will assign the highlighting of the rest of the code block to Reason. The problem is with the start pattern for the syntax injection, at.repository.reason-code-block.begin
.I've encountered this intermittently over a couple of years, but as I recently wrote a language extension for VS Code, I fired up “Developer: Inspect Editor Tokens and Scopes” and quickly found the issue. See how the scope changes to
meta.embedded.block.reason
after writingre
earlier in the code block. (Although my theme is Adapta Nocto, I tested that it has the same behavior with the default.)I'm aware of this extension's deprecation and expect nothing to come of this, but I figured I'd report it, since I had already triaged it.
The text was updated successfully, but these errors were encountered: