Skip to content
This repository has been archived by the owner on May 17, 2019. It is now read-only.

Add workaround for hotreloading when there are no store changes #72

Closed
ganemone opened this issue Feb 9, 2018 · 0 comments
Closed

Add workaround for hotreloading when there are no store changes #72

ganemone opened this issue Feb 9, 2018 · 0 comments

Comments

@ganemone
Copy link
Contributor

ganemone commented Feb 9, 2018

When any file is hotloaded in the browser, for example a react component, fusion will re-run the middleware stack. This is the correct behavior as that is what sets up context providers and eventually renders the application. However, in the case of redux, we don't want to recreate the store as it will result in warnings and potential loss of state. This adds a cache in the browser to ensure that you only create your store once.

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

No branches or pull requests

1 participant