OCapN: automerge marshal plugin PoC #2961
Draft
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.
Tagged-based "marshal plugin" for the OCapN client to send and receive Automerge document handles as objects.
This is a proof of concept for marshal plugins
Notes:
sync.automerge.org
sync server.Promise<DocHandle>
(result ofrepo.find
) but could likely beDocHandle
if usingrepo.findClassic
or somethinghandle.doc()
) should be json-serializeable plain objects but in actuality don't seem to be Compartment-safe, seems like they might be exposing some internal machinery. hardening such a doc seems to break automerge internal syncing + networking. I did not investigate further.