Is there any don'ts I should be considering with h...
# compose
g
Is there any don'ts I should be considering with having a object in a mutable state that itself has a state var in it?
z
Just that state object reads are more expensive than normal property reads, so if you have super deep nesting it could get real expensive. But behavior wise, no that’s fine
g
Cool, it's only 1 state inside another object that itself is a state - just a paginator object that itself contains a statelist. Just wanted to make sure I wasn't going to run into obscure bugs later, thanks!
z
You shouldn’t, but the thing about bugs is you don’t know they exist until someone finds them 😜