Daniel Dimitrov

We managed to migrate parity 2.3.6 database with the db-upgrade-tool and then to successfully start the openethereum client. It's now working for a couple of hours and it looks good....

Yep, sounds like what I had. My listeners were being unmounted. If you set `oneListenerPerPath` we'll set the listener the first time you need it and afterwards if you try...

similar to that problem maybe? https://github.com/prescottprue/redux-firestore/issues/88

@jeanregisser - check my pull requests if you want. For me it seems to solve the storeAs problem.

@prescottprue - please have a look at the pull request. I just did the same change in the case where there is no storeAs and meta.path So far it looks...

Hm, maybe I missunderstood the docs: { collection: 'cities', doc: 'SF', subcollections: [{ collection: 'zipcodes' }] }, thought that this would get me the cities/SF + cities/sf/zipcodes? but it seems...

Well, actually - once you know that you can't do it in one go it's a no-brainer. Maybe we should change the docs and mention this behavior? You can't fetch...

@JoshSum - before firestoreConnect is called - your redux selector is being executed. So if in the selector you return {docId: myDocId} and you change your firestore connect to accept...

``` firestoreConnect(props =>{ const daily = props.name // No daily, no need to subscribe to any document in firestore if(!daily) { return [] } return[ { collection: 'users' }, //

This should fix it? https://github.com/prescottprue/redux-firestore/pull/144