I got pretty far in a rewrite here to stick to the Hooks rules. I tried aligning this implementation closer to how Leptos impl. looks. I do get some issues with generational references though when I'm trying to loop over the rows in the template, but otherwise things looked promising.
Correct me if i'm wrong, but with hooks rules etc., this feels a lot more like react useState, than actuals signals. I think read/write separation would have helped me in this implementation, because it's harder to carry a mutable reference around in the rsx!, e.g. when looping over the rows, when i technically only have to read the signal to do that.
I got pretty far in a rewrite here to stick to the Hooks rules. I tried aligning this implementation closer to how Leptos impl. looks. I do get some issues with generational references though when I'm trying to loop over the rows in the template, but otherwise things looked promising.
Related to
Correct me if i'm wrong, but with hooks rules etc., this feels a lot more like react useState, than actuals signals. I think read/write separation would have helped me in this implementation, because it's harder to carry a mutable reference around in the rsx!, e.g. when looping over the rows, when i technically only have to read the signal to do that.