New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support change detection #9
Comments
I guess I should change the scope to add/remove, because that's the only thing we can detect on an entity. |
So I tested field-based changes, and while JS is a wonderful unicorn chewing gum and I can easily implement it, the performance is actually very bad (using Object.defineProperty.set) - especially for continually changing fields. Even if I create a wrapper which can be applied only to interesting components, it's bad. Iteration is faster if you just copy values over in a system, so that's what I recommend to do. Don't wait for mutation, just copy it. With that, change events are handled. That's one of my oldest tickets, so cheers to closing it! |
Fire events when components are created, components are added/removed and deleted.
The text was updated successfully, but these errors were encountered: