Closed davidtinker closed 8 years ago
Hello @davidtinker. You are right indeed. I forgot this. Would it be possible for you to sketch a PR fixing the issue for mixins and higher-order components etc. also please?
This should be fixed with the latest version of the library. Do you need a retro-compatible fix?
This causes problems with components using cursor paths with properties in them when they attempt to change the data via this.cursors.
Elsewhere:
Once properties have changed this.cursors will point at the wrong set of cursors.
The fix in mixins.js is simple:
I can send a PR if you like but its only 2 lines of code to add.