-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Access to component full state #73
Comments
Could be part of the Very excited to hear you're working on HMR, this is great news! |
I don't see any harm either. Currently the I'll work on a PR for Unless there was a way of extending the component skeleton that would let you mess with a nice clean pattern, creating your own "Heavy" base component. PS: Using this as a learning experience to understand HMR better 😄 , looking forward to integrating it with svelte-loader |
included in v1.0.5 |
While trying to get Hot Module Reloading for webpack going I couldn't find a way to access the full component state.
I think this feature could also be useful for storing/restoring session state from top level components. The
observe
callback suffers from the same problem, but dispatching to state observers would take more bytes to handle.Not sure if this is a featured you should opt-in to, or if it should be part of the
get
method.The text was updated successfully, but these errors were encountered: