Feature Request: Go Templates Support

[timkofu]

Would it be possible to add formatting, autocomplete, and colorization for Go templates? (.tmpl)

[hyangah]

The prior discussion history is here microsoft/vscode-go#228

We hope gopls can support formatting and autocompletion (golang/go#36911)

How to provide syntax highlighting based on textmate or semantic highlighting provided through LSP future release - that still need to be figured out.

/cc @stamblerre

[stamblerre]

How to provide syntax highlighting based on textmate or semantic highlighting provided through LSP future release - that still need to be figured out.

I wonder if we could do this through LSP's upcoming semantic tokens feature: https://microsoft.github.io/language-server-protocol/specifications/specification-3-16/#textDocument_semanticTokens.

[stamblerre]

@hyangah: Should this be in the gopls on by default project? It seems to me like this isn't necessary to turn on gopls by default.

[gopherbot]

Change https://golang.org/cl/284095 mentions this issue: [release] package.json: do not claim for .tmpl files in stable version

[inliquid]

Any reason why *.tmpl extension is chosen? Most of the time I saw either *.gohtml or just *.html when Go templates used on web. And when working with html templates one would want both HTML and Go language features be present in editor at the same time, otherwise you'd have to manually switch language back and forth.

[stamblerre]

We are adding incremental support for templates, starting with files with the .tmpl extension (https://golang.org/cl/297871). In the future, we will expand this to include other file extensions and to include templates within strings in Go files.

[inliquid]

Any way to make vscode-go understand other extensions at an early stage? I'm building html templates and I can test how new features work in real life, but in order to do so, if I understand correctly, I would have to rename all templates to have *.tmpl? That would be not very convenient.