merging non-sibling stores about automerge-classic HOT 1 CLOSED

I discussed this question with @orionz on #1, and further explored on #4. The current behaviour is that if you independently create two stores, add some stuff to each, and then merge them, the merged result will contain the top-level keys from both stores. However, for any nested objects, the merge will pick either one or the other, and move the losing value to conflicts.

So in your example, the list of cards is a nested object, so the merge will pick either one list or the other, but not combine them. To extend your example:

const Tesseract = require('./src/tesseract')
let s1 = new Tesseract.Store()
let s2 = new Tesseract.Store()
s1.root.cards = [{ title: "Card A"}]
s2.root.cards = [{ title: "Card B"}]
s1.root.board_name = 'aMPL'
s2.root.background = 'blue'
s1.merge(s2)

s1.root
// { cards: [ { title: 'Card A' } ],
//   board_name: 'aMPL',
//   background: 'blue' }

s1.root._conflicts.cards
// { '178422f0-f558-4b70-bbf1-f63e8ede8b08': [ { title: 'Card B' } ] }

However, that's merely how it behaves at the moment. The real question is how it should behave, and that's a question for you :)

from automerge-classic.