vscode-restclient VS vetur

I happened to have learned about parsing expression grammars a few days ago and got really excited about writing my own grammar. As I was missing this VS Code extension when working on neovim, an idea popped up: What if I write an HTTP grammar and an execute request from an interactive prompt?

I've noticed that when creating HTTP requests using VSCode's REST plugin, it gives language-specific autosuggestions. Is there any way to get this behaviour in Neovim? For instance using the built-in LSP?

The REST Client extension is a really useful tool to have at your disposal. In this article, I've really only scratched the surface of what it can do. It's well worth taking a few moments to look through the documentation in GitHub to find out what it's capable of.

I've started using Restclient, a VS Code plugin [1]. It allows me to easily add test scripts/requests to my normal GitHub workflow and share them with team mates.

[1] https://github.com/Huachao/vscode-restclient

The first step is to enable the Volar extension and disable the Vetur extension. Volar is the new recommended extension to use with Vue 3 and typescript.

Volar is supposed to be the upcoming replacement for Vetur, the Vue.js lsp server. It looks like it's significantly better than Vetur; has anyone tried it in lsp-mode in emacs?

There is a known bug in Vetur, the Vue VSCode extension, where it takes forever (sometimes several minutes!) to lint Vue files on save.

Now, we can create regular ol' Vue SFCs, or single file components. By creating the whole component in one file, we get the flexibility of thinking of our components as one functional unit made up of HTML, JavaScript, and CSS. We can also write components in TypeScript or SASS if we want to. We can also get syntax highlighting since SFCs end up being fundamentally HTML documents. And with VSCode plugins like (Vetur)[https://vuejs.github.io/vetur/], development in SFCs has a lot of benefits going for it.

You didn’t give much info, but from what I can tell from your screenshot you are writing in Vue and therefore are probably using Vetur. In that case the only info I could find was an issue from 4 years ago that seems to say you should just turn off style validation.

Vetur - Vue tooling for VS Code