Does not follow VSCode standards

[Hezkore]

Is there a reason the extension doesn't follow VSCode standards? For example, the task system goes unused in favor for custom "run" and "build" commands.

[Delta456]

Nobody has been working on the vscode extension for a long time so it maybe outdated with the standards. The main focus is on stabilizing the Language Server and the Language itself :smile:

[nedpals]

Is there a reason the extension doesn't follow VSCode standards? For example, the task system goes unused in favor for custom "run" and "build" commands.

The V VSCode extension was originally built by some user in the early ages and was recently adopted as the official extension for VSCode. Currently, we don't have enough resources and time to study and implement the extension in a standardized manner. If you are concerned about it, feel free to contribute. This is open source after all. :smiley:

[danieldaeschle]

I was the last one that worked on it. Could you provide examples where it doesn't follow the standard? I have no experience so far.

[JalonSolov]

On example was listed in the original post...

"For example, the task system goes unused in favor for custom "run" and "build" commands."

[danieldaeschle]

That might be a small change..