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

Misleading ReadMe #72

Open
rajatpharmeasy opened this issue Feb 2, 2019 · 0 comments
Open

Misleading ReadMe #72

rajatpharmeasy opened this issue Feb 2, 2019 · 0 comments

Comments

@rajatpharmeasy
Copy link

"This can be problematic because we are treating several dispatches as all part of a single transaction, but in reality, each dispatch causes a separate rerender of the entire component tree, where we not only pay a huge performance penalty, but also risk the redux store being in an inconsistent state.

redux-pack helps prevent us from making these mistakes, as it doesn't give us the power of a dispatch function, but allows us to do all of the things we were doing before."

This statement builds a notion in my mind that by using this library, I will have less rerenders of the component tree, which is not true, in an async action atleast two rerenders will happen, once for loading state being set to true, another when loading is done and data is available.

Each dispatch doesn't cause rerenders, change in app state does, which happens in this library's case also.

Although I enjoy the less boilerplate, more simple and readable code made possible by this library, but I don't see how it optimizes the process.

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