Closed grofit closed 8 years ago
I also thought it didn't work but you need to pass a second argument that is a string of one of the properties not sure if it matters that it is a property but it does need the second argument to actually call the watcher.
ah ok, its a moot point for me now as I ended up writing my own model watcher as I also needed full path resolution of property names, but good to know this is how it works.
If I were to do the following: (here is a jsfiddle https://jsfiddle.net/ocwj075r/1/)
outputs:
I was expecting:
A) It would only raise a single update B) The new value would contain the value of the object
So is this a bug or is this expected behaviour as I was expecting
callWatchers
to manually check for updates outside of the loop? assuming you needed to expedite a change rather than waiting the 50ms.