bindings to concrete types not propagating correctly from template to collection #1839

Activity

1. sjmiles

   added

   p0

   on Jun 11, 2015
2. sjmiles

   assigned

   kevinpschaaf

   on Jun 11, 2015
3. pvmart commented on Jun 12, 2015

   

   pvmart

   on Jun 12, 2015

   More actions

   Might be related.
   Overwriting an object in array with the new one destroys binding.

            this.push('test', {value: 1});
            this.set('test.0.value',  2);
            this.set('test.0',{value: 3});
            this.set('test.0.value',  4);

   The result is 3 but in the model is 4.
   http://plnkr.co/edit/AH5SKoedUQgeyfBgsfWL?p=preview
4. kevinpschaaf commented on Jun 12, 2015

   

   kevinpschaaf

   on Jun 12, 2015

   Member

   More actions

   @pvmart Yep, they are the same root cause. A fix is in the works that should solve both this and #1854.
5. kevinpschaaf commented on Jun 12, 2015

   

   kevinpschaaf

   on Jun 12, 2015

   Member

   More actions

   This should be fixed by PR #1855.

   Confirmed it fixes repro case here:
   http://jsbin.com/ziseru/2/edit
6. sorvell

   closed this as completedin #1855on Jun 19, 2015
7. kevinpschaaf commented on Jun 19, 2015

   

   kevinpschaaf

   on Jun 19, 2015

   Member

   More actions

   Root cause here w.r.t. notifying based on individual dom-repeat instances' item changng was fixed in #1854.

   Note related issue opened here: #1913, regarding problems when primitive values are duplicated in the array.
8. kevinpschaaf

   added a commit that references this issue on Jun 22, 2015

   Disambiguate config fromAbove and local defaults, pass to _setProperty.

   ...

   c7fec1c