You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
One idea I keep coming back to related to this: what if we had multiple reconcilers? - or at least the capability to support multiple reconcilers?
It'd be really cool to have:
ShallowReconciler, like React's ShallowRenderer - this is used for unit testing. It renders only a component's root return value and its immediate children, and no further.
TestReconciler, like React's TestRenderer - this is also used for unit testing. It completely renders a component tree to a series of objects.
The reconciler is starting to get pretty darn big, complicated, and a bit convoluted.
I'd like to take another stab at rewriting it from the ground up with better-defined types, and to be a little bit more robust.
My wishlist for the new reconciler:
setState
behavior, resolving setState locking throws confusing errors from event listeners #56 and Suspend event listeners during reconciliation? #71The text was updated successfully, but these errors were encountered: