Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider render cycle options #93

Open
mattkrick opened this issue Jul 27, 2016 · 0 comments
Open

Consider render cycle options #93

mattkrick opened this issue Jul 27, 2016 · 0 comments

Comments

@mattkrick
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant