Introduce a patchwork-tool-storage-provider #15
Open
pvh wants to merge 1 commit into
Open
Conversation
…ecific documents to ensure tools can store configuration or personal-but-not-document-specific data somewhere.
✅ Deploy Preview for patchwork-base ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
This provides tool-id-specific (I suppose, technically, it's keyed on any string key) documents to ensure tools can store configuration or personal-but-not-document-specific data at the account level.
I've introduced this as a way of retiring the existing use of accountDocHandle in several tools. This PR provides the patchwork-base side of the provider, but most of the usage is in patchwork-tools.
Particular attention should be paid to patchwork-llm, which is unique in several ways, in that it is an automerge-distributed library and has its own config section.
I'm putting this up as a draft PR; please don't merge it yet!