You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, p.Items is never used the the app - PageView directly accesses the store. I'd personally prefer if the example worked as expected, but I've been unable to find a clean way to trigger the update.
If the store is loaded & the refresh triggered prior to vecty.RenderBody then a panic is thrown.
I've found two ways to work around this issue without needing my list display component to directly access the store.
Upon first store load, delay dispatching the update by sleeping inside a goroutine for a short time. I think because of the batch singleton this should be reliable - Sleep(0) works for me for example. But feels like maybe one day it'll just stop working because of underlying threading models.
Add an isFirstRender bool to the example.go block above and move the store load to just before RenderBody. This works, but generally feels like it won't scale well with many components.
I'm going to use #1 for now because it scales better and should be pretty reliable.
Side question - how active is Vecty? It seems quiet - which is great if most things generally work :)
Thanks!
Brad
The text was updated successfully, but these errors were encountered:
Careful- Sleep(0) is documented as a call that should return immediately. Use time.Sleep(1) or runtime.Gosched() to guarantee a sleep of sorts.
As far as the correctness of the todomvc example goes, I remember reading it a while ago and thinking it could be done simpler. I think they're due for a rewrite.
As for the quietness- yes, it's been pretty quiet around here. Vecty itself works and as far as I can tell most if not all bugs I've run into have been from my own doing.
Hi folks. I'm learning Vecty by following the Todo example. In the example.go file there is this block of code
However, p.Items is never used the the app - PageView directly accesses the store. I'd personally prefer if the example worked as expected, but I've been unable to find a clean way to trigger the update.
If the store is loaded & the refresh triggered prior to vecty.RenderBody then a panic is thrown.
I've found two ways to work around this issue without needing my list display component to directly access the store.
Sleep(0)
works for me for example. But feels like maybe one day it'll just stop working because of underlying threading models.isFirstRender
bool to the example.go block above and move the store load to just before RenderBody. This works, but generally feels like it won't scale well with many components.I'm going to use #1 for now because it scales better and should be pretty reliable.
Side question - how active is Vecty? It seems quiet - which is great if most things generally work :)
Thanks!
Brad
The text was updated successfully, but these errors were encountered: