Enhanced syntax support

[Igorgro]

It would be great if this extension provide enhanced support for taskfile syntax, such as task reference autocomplete, clickable task references, semantic highlights, "run task" codelenens (similary to jest extension). All this will require development of custom language server like for example ansible language server for ansible vscode extension

[andreynering]

There's a language server made by someone else that stopped being updated at 2020 but that we could potentially use as a reference to build a new one: https://github.com/paulvarache/taskfile-language-server.

@Igorgro My summary is: I see value on all of this, but given this extension is pretty new, keep in mind that it can take a long time until we have all these features (if at all), specially if they require a language server, which means more work.

[pd93]

This is definitely on the roadmap. At the moment, we're relying on the YAML extension to provide schema suggestions too. It would be nice to bring all of this into the Task extension, but as @andreynering said, it may take some time.

My current plans are to resolve the issues with output window/terminal first. There's also a couple of performance related issues that the next release will fix. This will give us a stable base and we can then start to look at what will be needed to create an official LSP.

I'm quite excited by the creation of a first-party tool that will make use of Task as a package. This will allow us to do some dogfooding of the package API which is often overlooked as it is much less used than the CLI.

[ssbarnea]

Adding and maintaining a LS implementation is not easy task and because config files are already using YAML the difficulty is even worse. I would advise instead on building on top of YAML extension and contributing to it an addition for recognizing the expansions. That would be enough. Adding YAML extension as a dependency of this one would address the issue without having to add a custom LS.