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...

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...

@oliverpool I'm aware of this option, but not sure how it helps. Generally I would like to have support of go templates when working on `*.html` files with HTML language...

From further experiments it was found that in order to trigger application update you need: 1. Rebuild wasm binary 2. Rebuild and restart server 3. Close browser tab and reopen...

I think it shouldn't be required to recompile and restart the server, forcing to close open connections, background jobs, and generally stopping the service, etc, when changes are only on...

server is very generic: ```go package main import ( "log" "net/http" "github.com/maxence-charriere/go-app/v7/pkg/app" ) // The main function is the entry of the server. It is where the HTTP handler //...

> 1 and 2 are normal. 3 should not be required. However, I found it's required.

Server can monitor modification date and update service worker without the need to restart. Right now it compiles template-based `app.js` once at startup. Template can be recompiled. Needing to restart...

Second thing is a requirement to reopen the tab, but it involves JavaScript, which I'm not expert on, but from some high level research I saw that it should be...

> There is no requirement to reopen a tab. The update when there is a new version is not instant. You can track the behavior by opening the browser console....