Hey guys, I am trying to get multiple subcollections from a collection using firestore connect. I get the data correctly in firestore.collectionName.data but i get only the last subcollection data in the firestore.collectionName.ordered. Is there a way to use aliases instead of overwriting the variable names in ordered.
firestoreConnect(props => [
{ collection: "matches", doc: props.match.params.matchId },
{
collection: "matches",
doc: props.match.params.matchId,
subcollections: [{ collection: "firstInningsBatting" }]
},
{
collection: "matches",
doc: props.match.params.matchId,
subcollections: [{ collection: "secondInningsBatting" }]
},
{
collection: "matches",
doc: props.match.params.matchId,
subcollections: [{ collection: "firstInningsScore" }]
},
{
collection: "matches",
doc: props.match.params.matchId,
subcollections: [{ collection: "secondInningsScore" }]
}
])
Thanks scott, thanks for this wonderful package
@prescottprue I'm trying to connect firestore to redux-form. Firestore doesn't receive data/ordered until LISTENER_RESPONSE is called but by then I already have gotten an error that variable is undefined. I'm following the docs and using the compose/connect method for class components:
firestoreConnect(props => [{ collection: `petParents/${props.profile.ppid}/pets`, storeAs: "pets" }]),
connect(state => ({
pets: state.firestore.ordered.pets
})),
connect((state, props) => ({
initialValues: {
contactInfo: {...state.firebase.profile.contactInfo},
vetInfo: {...state.firebase.profile.vetInfo},
emergencyContacts: [...state.firebase.profile.emergencyContacts]
}
}))
That data gets to props eventually once LISTENER_RESPOSNE is called by firestore but not before i get an undefined error. What am i doing wrong?
@eleventhaus You will need to wait for data to load before using it, especially when initializing a form like that (otherwise the form well need to be reinitialized once the data comes in, which will require an option passed to redux-form). Also note that in that same part of the docs there are examples for how to do the same with HOCs using recompose.
@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.