Peter Fern

@gernest the `render variable` is internal to vecty. You are right to suspect the `Children` field to be responsible for your woes - you could try pulling in my patch...

I prefer the long-form names personally, and I wish HTML used the long-form for clarity too - you can see that this has consistently been the trend for elements introduced...

Quick brain-dump on the strategy I've been leaning towards. @glorieux wrote: > Why not use encoding/gob for data transfer? I've been using [pdf/websocketrwc](https://github.com/pdf/websocketrwc) as a thin wrapper to [gorilla/websocket](https://github.com/gorilla/websocket) (since...

> One solution could be to provide an interface the user can satisfy to prove equality of a property. I'm not sure how that would work, but we could probably...

> Could someone clarify for me which properties are allowed to be non-comparable types? Whilst user-defined properties are somewhat frowned upon they are valid, and may contain arbitrary data. Though...

Ouch, that's the brutal way of doing it (headless chrome).

@shurcooL can you provide steps to repro?

Thank you, any way to build the frontend with sourcemaps so I can attach a debugger?

> Also, I want to note it's possible the issue is because I haven't added `vecty:"prop"` struct field tags anywhere. I suspect that's the case: the `Checking for updates...` child...

I suspect just tagging the embedded `*model.RepoPresentation` would probably do the job, what's the trick to get the frontend to recompile?