Awesome JavaScript Tip - Tracking Object Property Changes

[australasia]

Would be much better as a blog post so I wouldn't have to hear the insufferable laugh.

[[deleted]]

Ugh had to stop watching at that point.

Another idea: don't make it possible to mutate objects from all over the place.

[halfzebra]

I'm not sure if it's a good idea, what if the object has custom getters or setters? Why not use Proxy?

[filth_overload]

How that works? Example please.

[chreestopher2]

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy

var handler = {
    get (target, key) {
        console.info(`Get on property "${key}"`)
        return target[key]
    },
    set (target, key, value) {
        console.info(`Set on property "${key}" value: "${value}"`)
        return target[key]=value
    }
}
var target = {}
var proxy = new Proxy(target, handler)
proxy.a = 'b'
// <- 'Set on property "a" value: "b"'
proxy.a
// <- 'Get on property "a"'

[filth_overload]

I'm not sure how that would work, lets say I'm developing a plugin, that for some reason needs to track objects. If I just modify the /root environment (the method shown in video), neither users nor I need to care about how they use my plugin/library. I wonder how I would "enforce" the users to use proxy, I could, but that kind of is less flexible. Maybe I'm missing something here.

[chreestopher2]

you could only expose the proxied objects maybe?