Looks to me like this.set('array.index.prop') is not notifying the dom-repeat, and the splice operators aren't notifying on the static paths. And unshift is apparently just confusing everyone.

Help us, @kevinpschaaf, you're our only hope!

Re-running the plunkr sample against your branch, it looks like the dom-repeat is now registering correctly, but the static bindings are still wrong:

http://plnkr.co/edit/M6BodZU902ZLlCesVKEL?p=preview

@pvmart As I mentioned on #1839, the root cause of that issue plays into what you were seeing here. However, I didn't quite grok that you were binding directly to array indicies in your example. The binding system does not support updating bindings to explicitly de-referenced array elements like this (what you're seeing is a side-effect of how we uniquely key array elements and send path notifications of which keys change, rather than which indicies get updated for better performance, so the 0 in test.0.value is interpreted by the observation system as a key, not an index, and what results is actually correct per the keys you indicated, but that's clearly not what you wanted). We may put supporting this on the roadmap, but it may not be something that we prioritize soon.

However, the binding/observation system exposes enough hooks for you to do this manually (i.e. what we're lacking in the system is just the ability to set up what I describe below implicitly based on inferring that you are binding to array indicies, but it's fully possible to wire it up yourself).

You can write bindings that use an inline function to help dereference the array and keep the value in sync when the array mutates, like {{arrayItem(test.*, 0, 'value')}}, where arrayItem is defined like this:

arrayItem: function(change, idx, path) {
  return this.get(path, change.base[idx]);
}

The test.* dependency to arrayItem causes it to be called for any updates to the array, and it then uses the get helper function to dereference the array with the index & path specified in the binding (note I'm using the optional 2nd arg to get to provide a different root from which to dereference the path).

Your code would then look like this:

        <div>[0] <span>[[arrayItem(test.*, 0, 'value')]]</span></div>
        <div>[1] <span>[[arrayItem(test.*, 1, 'value')]]</span></div>
        <div>[2] <span>[[arrayItem(test.*, 2, 'value')]]</span></div>

I updated your JSBin below using the #1855 branch, so once that fix lands you should be able to use this workaround.

http://jsbin.com/nasafe/3/edit

Thanks @kevinpschaaf -- it looks like I've got this wrong in the docs.

https://www.polymer-project.org/1.0/docs/devguide/data-binding.html#path-binding

I'm somewhat confused by the distinction between keys and indices here, and exactly how we should communicate this distinction. But it sounds like the short version is:

• associative-array/hash style access: use {{record.field}} in place of (0.5-style) {{record[field]}}
• standard array access: use a helper like arrayItem, above.

With 1839-1854-kschaaf branch changes made by push, pop, shift, unshift not propagating to dom-repeat if called asynchronously.

http://jsbin.com/kiwacasiju/1/edit?html,output

Fix: https://github.com/pvmart/polymer/pull/1/files

Thanks-- I'll take a look at that. There were a few other issues with the branch that I'm working out, so it will be a little longer.

Root cause here w.r.t. notifying based on individual array element changes was fixed in #1854.

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

Testing:

this.set("list.0", {name: "changed a"});
this.set("list.1", {name: "changed b"});
this.set("list.2", {name: "changed c"});

results in dom-repeat to be updated now correctly.
BUT: Running this after the changes:

this.push("list", {name: "a new one"})

results in list.1 and .2 to stay changed, but list.0 is reset to the original value.
Why is this?

Demo:
http://plnkr.co/edit/lNVG2dDmJtuf7hh8Fxf3?p=preview

OK, might be this
https://github.com/Polymer/polymer/blob/master/src/standard/notify-path.html

 if (array) {
            var coll = Polymer.Collection.get(array);
            var old = prop[last];
            var key = coll.getKey(old);
            if (key) {   // THIS ONE
              parts[i] = key;
              coll.setItem(key, value);
            }
          }

path.0 works if you change

if (key !== undefined)

nothing here works anymore

@Alvarz Do you expect any response to your comment?

@zoechi hi! excuse me that behavior it's just i was really really mad because i'm getting big issues with data binding and all the post or guides or answer only work with version 0.5, i really dont expect any answer and again I really apologize for my behavior.

@Alvarz :D I suggest asking on StackOverflow about your actual problem, ideally with a Plunker/JSBin that reproduces the issue.

@zoechi Thanks I will do it!