Hans Raaf
Hans Raaf
I would try to an `OnInit()` or `OnMount()`, print debug the value and transfer it to an internal value `t`or whatever. But I still guess that you use that `NewLoginForm()`...
Yes. This is why somebody made #562. I still do not know why @maxence-charriere never commented on that PR.
That PR looks odd.
You create a hierarchy of components and use them inside each other. Look here https://go-app.dev/declarative-syntax for the "Nested Components" example. I noticed that you are using `app.Head()` which most likely...
> my "root" element will always have to be something like a div. To have Go-App internal update mechanism to work, it needs to have a single root node for...
@mlctrez Do I understand it right, that you added a "proxy" web socket to the application (backend) which the frontend then connects to, instead of using the NATS original web...
> This allows publishing the nats client endpoint as a websocket. I don't understand. Do you mean the "nats server endpoint" here? What is a given if you simply use...
@mlctrez Ah, yes, that makes sense for this use-case. I guess that also solves the problem with the nats.go web socket client forcing TLS on the connection because the NATS...
Hi, Just some quick thoughts of mine: 1. I think it is perfectly fine to run go-app from static pages and use indexedDB (I do it myself). 2. Hi, I...
> Regarding IndexedDB, https://github.com/hack-pad/hackpadfs is a possibility. I use IndexedDB quite a lot from inside go-app, but I use a nice JS-based KV abstraction to make it less cumbersome. That...