e1acf66143
[IMP] component: components key is now static
...
This is a breaking change!
closes #279
2019-09-11 11:18:49 +02:00
e6a3ede4a6
[FIX] component: improve unmount/remount behaviour
2019-08-28 11:41:10 +02:00
9b3a97e732
[DOC] component: improve internal documentation
2019-08-26 12:19:11 +02:00
9843d16585
[REF] component: improve render method
2019-08-26 10:31:11 +02:00
e690991a6a
[FIX] component: better heuristic to determine if was mounted
2019-08-22 14:55:31 +02:00
9754cc7521
[REF] small cleanup
2019-08-22 14:26:34 +02:00
ca920a0091
[ADD] router: initial implementation
2019-08-22 14:26:34 +02:00
e5b1ba24d8
[IMP] component: allow multiple mount/unmount
...
closes #258
2019-08-22 14:23:08 +02:00
fd0fb5be00
[REF] observer: refactor observer using proxy
...
closes #253
2019-08-22 14:22:20 +02:00
f18c73e59f
[FIX] component: solve a tricky concurrency rendering issue
...
When components were initially rendered more than once, in consecutive
microtask ticks, the order of two actions was reversed: the assignation
of the vnode to the __owl__.vnode property, and the assignation of
__owl__.vnode to the final rendered vdom of the component.
As a result, the widget was rendered as null (so, not present).
The reason for this issue was that the renderPromise key was reassigned
at some point.
2019-07-30 08:54:55 +02:00
93d0a7dd46
[FIX] store: properly handle defaultProps in connected components
...
Thanks to aku for issue + tests + first solution
closes #245
2019-07-16 20:51:57 +02:00
5382e824b1
[REF] owl: reorganize src code in sub files
2019-07-16 13:12:08 +02:00
Géry Debongnie