fix: force lazyStateGetterSettter dependents to rebuild on state change

[GregoryConrad]

Also fixes #32

[busslina]

So now we have to take care that we have always the last version of the getter. To not cache it

[busslina]

I propose you an alternative solution. To specify in the API.rebuild() a false by default argument to disable equality check.

Maybe not possible due to the design, which I haven't readed yet.

I have to review my code, but maybe I was catching the getter somewhere.

What do you think about this?

[busslina]

But I understand it could be tricky and a bad practice.

[GregoryConrad]

So now we have to take care that we have always the last version of the getter. To not cache it

You can use whatever version of the getter you like; they’ll all work. Only issue is the reactivity of dependencies, which is why I made that change yesterday. Feel free to cache it, just be careful t that you don’t then return a cached copy as your capsule’s data.

To specify in the API.rebuild() a false by default argument to disable equality check.

This will result in the same issue, but just pushed down to the next level of capsules (unless you force rebuild the entire dependents subgraph, but I don’t really think that’s a good idea).