Skip to content
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

Granular state changes #72

Open
JoshKarpel opened this issue Dec 29, 2023 · 0 comments
Open

Granular state changes #72

JoshKarpel opened this issue Dec 29, 2023 · 0 comments
Labels

Comments

@JoshKarpel
Copy link
Owner

Right now, when we detect a state change, we re-run the entire component tree. This is overkill - we can know which component the state changed in, and re-run only that component and its descendants.

  • This should result in some speedup because we'll be running less code overall, especially potentially-expensive things in components that we know didn't change at all.
  • We'll need some way to mark the dirty shadow node, and then to propagate that dirtiness to its children.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant