-
Notifications
You must be signed in to change notification settings - Fork 1.4k
doc: Storing State - edit pass #782
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
Conversation
| Qwik needs to track the application state for two reasons: | ||
| 1. Application state needs to be serialized on application pause (and deserialize on application resume.) | ||
| 2. Qwik needs to create subscriptions on stores so that it can know which components need to be re-rendered (if Qwik would not track subscription information then it would have to re-render the whole application which would defeat the lazy-loading.) | ||
| 1. To serialize data when the application pauses, and deserialize as the application resumes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would modify it to "pauses on the server" and "resumes on the client"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! That keeps it much more explicit
|
Thanks @craigshoemaker ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shairez - here's those tweaks :)
| Qwik needs to track the application state for two reasons: | ||
| 1. Application state needs to be serialized on application pause (and deserialize on application resume.) | ||
| 2. Qwik needs to create subscriptions on stores so that it can know which components need to be re-rendered (if Qwik would not track subscription information then it would have to re-render the whole application which would defeat the lazy-loading.) | ||
| 1. To serialize data when the application pauses, and deserialize as the application resumes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! That keeps it much more explicit
What is it?
Description
Edit pass
Use cases and why
n/a
Checklist: