Dart-Code VS Vim

If it is related to the Dart/Flutter plugin, you should file a bug for that project and not for Dart or Flutter.

You say that only thing I did was open an issue and take the credit. I take that feedback constructively, but one tiny contribution I did though is make the Dart extension use the new API.

I can't help with the first few, but if you're seeing slow performance writing Dart/Flutter, please file an issue at https://github.com/Dart-Code/Dart-Code/issues.

It would probably be better if you file an issue here: https://github.com/Dart-Code/Dart-Code/issues

You might want to look into Dart-Code how these closing labels are generated and then create another VSCode plugin to create your kind of code decoration. I had a 1min glance at the plugin source code and I think, this API is responsible to creating such decorations.

The DevTools are a stand alone web application that are integrated into VSC using a VSC-specific webview component. This integration is written in TypeScript. See here.

I'm not aware of any other formatters for Dart. There's an open issue about more flexible formatting at https://github.com/Dart-Code/Dart-Code/issues/914 but it's not something being actively worked on. If someone was to create their own formatter I've offered in that thread to provide some pointers for wrapping it up into a VS Code extension (the Dart extension already supports disabling its own formatter, although VS Code now allows you to more easily select a different formatter).

Also, there's already an official extension for Dart which is open source, have you thought about contributing this feature to that extension?

This fix: https://github.com/Dart-Code/Dart-Code/issues/3332

I find the Vim extension for VS Code has macro support that is good enough for most of my use cases (if you’re a fan of Vim key bindings - obviously).

https://github.com/VSCodeVim/Vim/blob/master/ROADMAP.md#repe...

that's why I just use https://github.com/VSCodeVim/Vim if I have to use VSCode

They have discussions enabled on the GitHub repository; eventually r/vscode might be of help.

What you would learn from using a neovim addon for VS Code covers most of the first point and some of the second - VSCode Vim lets you run neovim in a headless mode that relays keypresses to it, and emulates several popular addons. It also comes without quite as much hassle as comes from the second step of learning to configure vim/neovim yourself. Most VSCode extensions work pretty well out of the box, maybe requiring you to add the path to a compiler/interpreter that is not on your PATH.

The extension does have visualedit. You can check the list of supported features here: https://github.com/VSCodeVim/Vim/blob/HEAD/ROADMAP.md

I though VSCode's vim emulation had issues with code folding

Either I go with K552 or save for RK84 if not CB-GK-16 and both of these are pretty good choice that's certain, or I go with 617 Fizz and use VIM keybinding which Isn't an issue for me cause I've been using NeoVim for more than 1 year, you can grab my dotfiles if you want. Most people won't go with 60% cause they are used to arrow, home, end ... keys so am I with vs code but today I found out about vscodevim extension which enables vim keybinding , these keybindings pretty easy to use more than arrow, home, end .. keys if yo're a vim user like Shift + $ = end, Shift + 0 = home, in visual mode V to select text etc ...