Fixed incorrect changed path when mutating unrelated area of proxy during iteration operations on cloned areas of the proxy.

[brendon1982]

Hi,

I've been using your fantastic library in a side project, and I picked up an edge case that occurs when iterating over some part of the proxy and during that iteration modify a different part of the proxy. In this case the change path reported as the property currently being iterated over instead of the mutated property.

For example, if I have this object:

{
  a: [
    {
    quantity: 1
    }
  ],
  b: {
    c: {
      quantity: 8,
    },
  }
};

And I do the following:

proxy.a.forEach(() => {
  proxy.b.c = {
    quantity: 3,
  };
});

The expected change path is b.c, however, it is reported as a.

The issue seems to be that the handleChange would detect that a SmartClone is active, due to the forEach, and therefore branch into the logic for updating the clone without first checking if the change path applies to the clone.

[brendon1982]

Hi,

It seems like I failed pretty hard on the eslint side and have had to make additional commits to address the issues.

Would you prefer that I make a new pull request with everything squashed?

[sindresorhus]

Would you prefer that I make a new pull request with everything squashed?

No. I will squash on merge.