You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A major pain point with angularfire continues to be mapping a document ID to a collection query. I propose we add an optional withId argument to collection.valueChanges(). This can be a simple non-breaking change and I can PR it.
// current requirementref.snapshotChanges().pipe(map(actions=>{returnactions.map(a=>{constdata=a.payload.doc.data();constid=a.payload.doc.id;return{myIdKey: id, ...data};});})// after change ref.valueChanges('myIDKey')
The text was updated successfully, but these errors were encountered:
A major pain point with angularfire continues to be mapping a document ID to a collection query. I propose we add an optional
withId
argument tocollection.valueChanges()
. This can be a simple non-breaking change and I can PR it.This will greatly simplify the code below
The text was updated successfully, but these errors were encountered: