sachaw
Explore posts from serversForce effect computation, or alternate approach?
Not working correctly yet, but is reacting to changes (although positions are reseting and simulation does not restart)
https://gist.github.com/sachaw/f9c73aa1806ab26cd52b7c3237b02200
11 replies
Force effect computation, or alternate approach?
I tried D3 before this, which worked fine, but I need to be able to react to nodes or edges being pushed to my store and inseted reactively. The behaviour was either non-reactive or would reset the layout (positions) every time
11 replies
Nicest way of having computed properties in a store?
Since Getters are working now, is there a concise way to have side effects when the store is updated, withoug having a dedicated createEffect.
I want to be able to call a grpc endpoint on my server when certain state properties are updated.
13 replies
Nicest way of having computed properties in a store?
Must be something else in my application, this works as it should, I'll keep digging:
https://playground.solidjs.com/anonymous/6515f38a-c74d-4b51-b37f-5a2ede1a2005
13 replies
Nicest way of having computed properties in a store?
I was originally destructuring the state variable that I passed to the context provider, I have since changed that so it just passes
localState
, however it's stil not working:
This only ever gets fired once13 replies