I don't understand why VSCode itself doesn't already have this, since it is silly to have to install 100 extensions to add this behavior to every different possible place that a string literal with an interior language could appear
I also suspect that unlike the JetBrains feature that does this (Language Injection), VSCode doesn't understand the code it just syntax highlights it. Meaning if we take the cited example and change it to the following, would VSCode turn it red?
example3: | # js
console.ogl('wat")
9dev · 8h ago
Oh neat! Finally VS Code can do something IntelliJ has been able to do since decades. We’re so close to discovering why IDEs were a good idea in the first place!
IshKebab · 7h ago
VSCode is an IDE. It's just a highly modular one, so it doesn't come with everything by default.
mdaniel · 5h ago
I believe the splitting of hairs is that plugins should build on top of core, solid, helpful primitives, and augment the core platform with esoteric things that the core audience wouldn't care about. That's not this plugin
It also pragmatically makes for fragmentation in the experience, leading to the same outcome as the current LLM debate: "works great" "not for me"
imcritic · 4h ago
Who (and in which valid cases) embeds some block of code in a programming language as a value to some key in a YAML file??
I also suspect that unlike the JetBrains feature that does this (Language Injection), VSCode doesn't understand the code it just syntax highlights it. Meaning if we take the cited example and change it to the following, would VSCode turn it red?
It also pragmatically makes for fragmentation in the experience, leading to the same outcome as the current LLM debate: "works great" "not for me"