- Notifications
You must be signed in to change notification settings - Fork137
Fix broken example in the README.md#92
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
In the example store.setState was called with what could be a stale state. In order to use the current state, one must call store.getState. Similar to how in React if you call setState without a callback it is a potential bug.
boazberman commentedJun 16, 2018 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I've spent a lot of time searching for this API, and only found it in thedeclaration file. |
developit commentedAug 29, 2018
I believe there's another example that shows the getState() version - perhaps we'd be better off showing a synchronous function for this example? I just wanted to have a way to show both. |
boazberman commentedAug 31, 2018
Well, my difficulty was that I just could not understand how one can manipulate the state object after an async operation happened, and expect the results to be valid, as the state could change during that period, but the state object being manipulated is the old state. If you think there is no need in this example I understand, I just though it will save some people from having bugs caused by an asynchronous behavior. Thanks! |
In the example store.setState was called with what could be a stale state. In order to use the current state, one must call store.getState. Similar to how in React if you call setState without a callback it is a potential bug.