@eleventhaus Also, unreleated, but in the example you posted spreading objects into props like that could cause some rendering performance issues down the line (since re-renders happen every time props change, which will be happening every time). You may want to look in to selectors (a library called reselect helps)
So I tried using the isLoaded strategy but that only responds to changes in firebase. The data I'm waiting to load is in Firestore. When I check, isLoaded is true before Firestore data is loaded.
Should I use firestore.status.requesting instead? What's the best way to do that?
@prescottprue ah,
react-waypoint is a cool library but I'm already using react-virtualized. Sorry for being unclear. My issue concerns needing a different storeAs name for every page of listeners because, without it, each listener call overwrites the results from the previous page/listener. So, my workaround is to use storeAs and create a unique store name for each listener. For example, I store the first page in storeAs: 'items.0', 2nd batch in storeAs: 'items.1', 3rd in storeAs: 'items.2', and so on. I'd rather be able to store all listener results in storeAs: 'items', which makes my mapStateToProps simple: items: state.firestore.ordered.items || []. Otherwise I have to reduce all the state.firestore.ordered.items.n stores into items. I'm using reselect to memoize this, but it would be nicer if each page of listeners could just append the new page of items to state.firestore.ordered.items rather than using a different storeAs for each listener. Is that possible using a config option like mergeOrdered, allowMultipleListeners, or oneListenerPerPath?
@dustingraves maybe this will help? http://docs.react-redux-firebase.com/history/v3.0.0/docs/integrations/react-native.html
@prescottprue is there anything like profileParamsToListen in react-redux-firebase?
I want to add global listener to the app on connections/${profile.connectionId} node in database.
There is profileParamsToPopulate Api. The thing is that it doesn't listen some prop under profile continually, but only populates it once on every profile update.
I've found firestores filtering capabilities very limited so depending on your needs it might not even be possible with firestore alone
trying to use store.getState() in firestoreconnect, but can't seem to get it working. using 3.0
uhm
work please?
store === props is true
so im not sure what im doing wrong, or what i should do differentley, cant seem to access store. Maybe not available in 3.0?
so i dont have to deal with the weird -LD5..
saved it as lols obviously
Also - i tried accessing the store in firebaseconnect, but cant seem to do that either. Is this changed in 3.0? same issue as above
Anyways i solved it anyways.
trying to work with pagination, they do indeed get ordered right when ordering by upvotes
but when im trying to do ["upvotes", "desc"] everything just gets weird, and it only seems to order it by the limit you have set
i.e 1-10 only ordering these posts
10-20, only ordering those posts
but if i dont use desc, it works, but obviously in reversed order.
Hye, I want to ask regarding actionTypes.CLEAR_DATA to clear firestore data.. I use this one as a callback after user logout.. when I open another screen after that, the screen is calling firestoreConnect with collection but my firestore did not update again. does this is normal behaviour or did I did something wrong ?
