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
keep reactive computations synchronous with the render phase #1
Conversation
…ithTracker behavior - compare deps in order to keep API consistency to React.useEffect()
…cker() can be omitted - also React.memo() already has a check for prop change so there is no need to check for changed deps again
https://github.com/facebook/react/blob/d77d12510b1a1c37484d771a323e0a02cbeb9ba7/packages/react-reconciler/src/ReactFiberHooks.js#L231 https://github.com/facebook/react/blob/d77d12510b1a1c37484d771a323e0a02cbeb9ba7/packages/react-reconciler/src/ReactFiberHooks.js#L318-L329 https://github.com/facebook/react/blob/d77d12510b1a1c37484d771a323e0a02cbeb9ba7/packages/react-reconciler/src/ReactFiberHooks.js#L878 - update comments
… change), but allow async and computation reuse after.
# Conflicts: # packages/react-meteor-data/useTracker.js
… same as before, but is easier to read
Half duplex
…it asynchronously
This is good to go @yched. It retains backward compatibility with |
Any thoughts on this @yched ? |
Catching up :-) Since you opened meteor#271 on the main repo, I guess this PR here can be closed now, right ? (let's not fork the discussion more than it currently is ;-) ) |
superseded by meteor#271 |
fixes meteor#262