bug(reducers): multiple subcollections on same parent collection causes invalid merge

Here’s the scenario. This is React code with a router and I have two components on two different pages doing:

  firestoreConnect([
    { collection: 'group', doc: 'uJH3akkXRkje3ruPZ7au' },
    {
      collection: 'group',
      doc: 'uJH3akkXRkje3ruPZ7au',
      subcollections: [{ collection: 'objects' }],
    },
  ]),

And the other one doing

firestoreConnect(['group'])

Whenever I go from the first component to the second component,firestoreConnect on group would shallow merge the specific doc and removing the subcollection information stored in there, both on dataReducer and orderedReducer.

[Klabauterman]

I have the same issue even in 0.2.5. It is also a problem if you have two subcollections in the same parent document. Both are updating the parent document and the second subcollection update removes the data of the first one from the store-state. Maybe I could use storeAs as a workaround, but I think that is not a good solution.

[prescottprue]

@diagramatics Good to know. If you need a solution in the meantime you can use storeAs to place the data in different locations of redux and merge the data by hand.