Doesn't work when deleting properties about hyperactiv HOT 2 CLOSED

Hi @W4G1,

Yes this is an unfortunate limitation when using handlers but an expected behaviour nonetheless, since the base library only observes property mutation events (set/get).

As a workaround, you could either set the property to undefined instead of deleting it or write a Proxy that will mimic the property deletion on the copy object.

// Either:

obj.a = undefined

// Or:

obj = new Proxy(obj, {
    deleteProperty(target, prop) {
        delete target[prop]
        delete copy[prop]
        // or maybe just: target[prop] = undefined
    }
})
delete.obj.a

from hyperactiv.

That's unfortunate indeed, but understandable.

I'm currently using a mix of both workarounds you mentioned.

I use a Proxy trap — deleteProperty() — to catch the property deletion where I first set the property to undefined which triggers the __handler method. Then I actually delete it from both objects.

from hyperactiv.