Joseph Heck

possible PR to resolve (the strict "throw error on ID already in repo" concept): https://github.com/automerge/automerge-repo-swift/pull/82

I think this does beg for a repo-based API that allows merge - it would be just a light wrapper around `document.merge`, but would at least be conceptually sound. A...

I think I get the concept you're proposing - not opposed conceptually, and connect, while an overloaded term, is pretty good for what you're after. A couple of quick questions:...

Short answer to the question above: > That you are talking about a scenario where the Repo is not managing it's own storage? Is that correct? Yes - outside of...

I'm very loathe to remove the ability to import/create a document with an ID. The ID is the only indicator that "this is the same document/documents can be 'safely' merged"...

Mostly. It certainly does for the bundle "load from filesystem" scenario, and is well supported in the Apple scenarios. The place where it isn't as well supported is in mechanisms...

Happy to help provide references: For the drag and drag, one-binary-thing I was mentioning, the bits that Apple started pushing is called "Transferrable". I wish there was more to read...

Yeah, I was recalling something like that as well. I added a to-do item for myself to create a test to validate everything is working as expected with #62 -...

I think what you're trying to do it create an array of dictionaries, keyed by strings. This technique - one CRDT inside another - is what we've been calling nested...

I was just popping here to report the same thing, saw this, so didn't want to explicitly dupe. With the beta4 Xcode, the compiler is crashing (with the tag `0.9.0`...