describe how caching of data works #58
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
tantaman
changed the title
tantaman
force-pushed
the
mlaw/caching
branch
from
9cefb43 to
3a04272
Compare
|
Until somebody (cough: me) sacks up and writes the design doc perhaps this makes sense in the preloading section? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The thread on UI flickering (https://discord.com/channels/830183651022471199/1322102519987572747) showed that a few users misunderstood how data was evicted from the device.
I think we ultimately need a "How Zero Works" or "Concepts" section.
edit: Converting to draft. I don't like the notice in this section.