Géry Debongnie 6465665550 [FIX] qweb/component: handle nested t-foreach and components ...

The way keys were handled in QWeb was mostly ok, but a little naive. It
is fine when we deal with a list of dom nodes, since the reconciliation
algorithm need only to be able to differentiate/reconcile nodes in that
list, but it is an issue with components, which needs to globally be
able to find themselves in their parent's children map.

Because of the way this was handled, there were situations were Owl
internal virtual dom would crash, since components wrongly assumed that
they were already rendered in a different place.

To fix this, we generalize the way keys are generated, by concatenating
all sub keys coming from each iteration loops.

closes #584

2019-12-17 15:23:24 +01:00

..

__snapshots__

[FIX] qweb/component: handle nested t-foreach and components

2019-12-17 15:23:24 +01:00

component.test.ts

[FIX] qweb/component: handle nested t-foreach and components

2019-12-17 15:23:24 +01:00

props_validation.test.ts

[IMP] component: allow custom validator functions for props

2019-11-22 15:43:22 +01:00

slots.test.ts

[REF] tests: remove Widget common class

2019-12-11 12:25:05 +01:00