Géry Debongnie ed4ab51c17 [FIX] component: tricky concurrency issue ...

This is a really interesting problem: there was a situation where a
component would not have an event handler properly bound. The reason was
that we were in a situation where the scheduler task queue was flushed
at an unfortunate timing:

- parent component template is rendered
- subcomponent is prepared:
   - sub component is willStarted
   - it is rendered (so, fiber counter is set to 0)
- scheduler task queue is flushed => we patch the DOM
- the code registered in the __prepare.then(handler) is executed, which
  add the createHook to the vnode (but after the dom is patched)

Usually, the last two steps happen in a different order, but in an
environment with connected components, we sometimes flush the task queue
at various moments, so some code could be executed between the end of
__prepare and the registered handler.

The fix is interesting: we give a callback to the __prepare function
instead of registering a .then handler to the deferred.  This callback
is then guaranteed to be called at exactly the proper timing.

Thanks seb for the hard work of finding the root cause of this issue

closes #520

2019-12-03 08:23:10 +01:00

..

animations.test.ts.snap

[FIX] component: tricky concurrency issue

2019-12-03 08:23:10 +01:00

store_hooks.test.ts.snap

[REF] store: replace ConnectedComponent by useStore hook

2019-10-14 11:06:59 +02:00