Recent fixes
output: The change seems to be already done when onValidate is called.
Fixes this error when proxying ArrayBuffers:
Hello, I am using on-change to watch changes in the state of my application. Until now, I was using the default configuration. With this, when I listen to a change in my list, if I add a new element in my list, the path I get in the onChange method if the array itself. For example: And when I do , then the path in the onChange method is . Now, I add some problems with some functions like , which were not triggering all the events, but only one event at the end of the loop. So I've tried to activated the options, as documented. This worked well, except that now the path has changed when I add elements in my list. For example, now I have: And when I do , then the path in the onChange method is now . I don't really understand the philosophy here. Is it intentional? Is it a bug? (I could perhaps try to sove it by myself in a Pull-Request, but I would be happy to discuss this before.) Thanks.
Structured data for AI agents
Repository: sindresorhus/on-change. Description: Watch an object or array for changes Stars: 2027, Forks: 88. Primary language: JavaScript. License: MIT. Topics: change-detection, es2015-proxy, nodejs, npm-package, object, watch. Latest release: v6.0.2 (5mo ago). Open PRs: 0, open issues: 0. Last activity: 5mo ago. Top contributors: DarrenPaulWright, sindresorhus, BendingBender, hpx7, kpruden, albertosantini, Seldszar, brendon1982, franciscop, glundgren93 and others.