Géry Debongnie f2b3ebd1ec [FIX] component: properly set currentFiber to null in all cases ...

Whenever a rendering is completed, we need to reset the currentFiber
to null to make sure all subsequent renderings will not be
confused.

However, the way it was done before this commit was wrong in a
specific situation: we resetted the currentFiber to null in the
patch method.  The idea was that this method was called every time
the component completes a rendering. But this is not true: it
can happen that a component is unmounted and remounted without
changes.  Then the component will be patched, but if there is no
change, it will not call recursively the patched methods of its
children.

So, we need to choose a better place to reset it to null.

closes #454

2019-11-14 11:56:13 +01:00

..

__snapshots__

[FIX] component: concurrent rendering issue

2019-11-12 10:01:12 +01:00

component.test.ts

[FIX] component: properly set currentFiber to null in all cases

2019-11-14 11:56:13 +01:00

props_validation.test.ts

[FIX] component: fix invalid prop validation situations

2019-11-14 09:27:09 +01:00