The thing is you've sort of already seen it. Global state and local state are the same. Since signals and effects have nothing to do with components you can just use those for global state as well. We also have a proxy for deeply nested reactive state that is useful in these cases.
Okay fine... I'll try out Solid soon. The more code I get to throw out while still maintaining understandability is awesome and it looks like Solid is going to get that done for me :)
first question: can you have an effect with 3 dependencies inside, but it's only triggered when two of that dependencies update? there are use-cases like this, and I don't see if we can handle it here second: if effect must trigger function from props, what's the implications of that? I mean, if we pass that function as a prop, how does Solid know, if function is the same?
I am using solid and I am loving it. It's easier compared to react hooks.
Solid just makes sense.
Can't wait to use it. Would like to see more global state examples. Right now I really like Recoil but that's React.
The thing is you've sort of already seen it. Global state and local state are the same. Since signals and effects have nothing to do with components you can just use those for global state as well. We also have a proxy for deeply nested reactive state that is useful in these cases.
Nice! Loved the shoutout to Jotai
Okay fine... I'll try out Solid soon. The more code I get to throw out while still maintaining understandability is awesome and it looks like Solid is going to get that done for me :)
first question: can you have an effect with 3 dependencies inside, but it's only triggered when two of that dependencies update?
there are use-cases like this, and I don't see if we can handle it here
second: if effect must trigger function from props, what's the implications of that? I mean, if we pass that function as a prop, how does Solid know, if function is the same?
i already been through such hook-up..
Nice