feat: persist the tree and file content through an optional store - #7
Merged
Merged
Conversation
Merged
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Every process re-downloads the tree and each document, so the Prompt docs reader waits ~1 s per document and nothing works offline.
DocsClientOptions.store({ read(key), write(key, value) }) persists the tree and file content. Content is keyed by its git blob sha and only reused when it hashes to the sha in the current tree, so it is never stale and a corrupt entry is ignored.DocItem.shacarries the blob sha from the tree.peekAll()returns the known tree without a request, for showing a list before the network answers.In Prompt, reopening a read document drops from ~1 s to 15–31 ms, and read documents open offline.