Proxies are a turtles all they way down approach for things like this,
don't return the actual property, return a Proxy to the property that can
have reference to the path used to get there. However, this ruins
performance, and cannot represent primitives as values. A function for full
path
Doesn't sound like you think much of the proxy approach, then Bradley! lol
So the approach I originally took is more in line with what you'd recommend?
Rob
On Thursday, January 31, 2013 4:44:26 PM UTC, Bradley Meck wrote:
Proxies are a turtles all they way down approach for things like this,
I really like proxies, but they are not a cure all; in some situations they
are very very beneficial (NodeList in the DOM spec for example), but they
do not like valued tree structures.
But yes a function that delegates out to a tree structures is what I would
recommend.
--
--
Job Board:
I use something closer to observables (with a little bit of proxy type
code) for doing this kind of work, it works by caching data into objects
and then saving the observed changes. There is quite a lot of plumbing to
get this running but so far I have been able to abstract over different
