performance is already pretty dang good.
BUT, if we make a react-cashay wrapper, we could encapsulate redux so we don't even call cashay unless a cashay action is called, essentially, it wouldn't respond to the redux listeners.
If we did this, we could reduce complexity by removing dependencies. This frees up memory, but it still means every time a cashay query or mutate is called, we'd have to recalculate it from the tree. I'll have to see how CmRDTs work out before leaping off this bridge.
Alternatively, we could allow options to be a function (state, props) => options. This pales in comparison, but it'd still be nice not having to create an options object just to dump it by the wayside when we realize what we want is already cached.
performance is already pretty dang good. BUT, if we make a react-cashay wrapper, we could encapsulate redux so we don't even call cashay unless a cashay action is called, essentially, it wouldn't respond to the redux listeners.
Alternatively, we could allow options to be a function
(state, props) => options. This pales in comparison, but it'd still be nice not having to create an options object just to dump it by the wayside when we realize what we want is already cached.