Help with front implementation

[warm sage]

there are libraries like gomponents and templ that can make it less painful. but at the end of the day ur browser can't run go (unless u compile for wasm) so it'll be kinda weird. go's stdlib has templates that work ok but i think they are pretty ugly. someone else will probably have better advice

[forest remnant]

Nono of course, I meant what’s the good practice for my frontend to interact with my backend

[warm sage]

oh i gotcha.

generally my flow is, when the user goes to a new page, it should await an asynchronous function that makes an api call to get whatever data it needs to populate that page

[forest remnant]

Like would this be valid?
func main() {
mux := http.NewServeMux()

mux.HandleFunc("/login", loginHandler)

http.ListenAndServe(":8080", mux)

}

func loginHandler(w http.ResponseWriter, r *http.Request) {
http.ServeFile(w, r, "templates/login.html")
}

[warm sage]

I believe that would be okay yes. u can also serve a whole filesystem which is fairly common for using frameworks

[forest remnant]

I understand how to do it inside js, but no how to tell Go to leave to a html file in certain cases

[warm sage]

like to go to a new page?

[forest remnant]

Oh ok, thanks, I’ll search it

[forest remnant]

Like in the example “for /login leave it index.html”

[warm sage]

I think that'd be fine. but hopefully someone else can give feedback as well. in general: do it as simply as possible for right now and only add complexity when u feel it's necessary.

[forest remnant]

Okok thank you!