It seems the components using the collection as a prop are never re-rendered when the collection is updated.
The bindReactiveData() callback does run, but the state is never seen as "changed" by Redux's combineReducers() (see the use of 'hasChanged' var in combineReducers, it's always false after the meteoredux reducer).
So even though the store does hold the updated content of the collection, the components that depend on it are not re-rendered.
It seems that's because the updateData() function in meteoredux.js modifies the current state in place, instead of copying it ? (the code has a comment about that :-)
It seems the components using the collection as a prop are never re-rendered when the collection is updated.
The bindReactiveData() callback does run, but the state is never seen as "changed" by Redux's combineReducers() (see the use of 'hasChanged' var in combineReducers, it's always false after the meteoredux reducer). So even though the store does hold the updated content of the collection, the components that depend on it are not re-rendered.
It seems that's because the updateData() function in meteoredux.js modifies the current state in place, instead of copying it ? (the code has a comment about that :-)