Keep ID in document.data() about firestore-jest-mock HOT 4 CLOSED

Hmm. So you have an additional field in your documents that are a copy of the id itself? That feels tricky, as the default behavior of a document is to return the id separate from the data() -- but if you have a field on the document called id as well, that's trickier and feels like an edge case.

For your side question, you should be able to do it in the same file, but not within the same describe block. Jest will hoist mocks to the top of the function, regardless of where you declare them. So if you wanted to test those two cases, you would need two distinct describe blocks.

from firestore-jest-mock.

Yeah it's a workaround, as the collectionGroup cannot get by id. To allow us to use similar context for doc(id).get() and collectionGroup(collection).where('id', '==', id). This workaround is so that we can find a record directly without having to carry around the multiple ids to taverse the whole tree to get to that record.
It is a common issue for firestore queries, and this is a popular solution for it.

from firestore-jest-mock.

Hey @HauptmannEck, can you take a look at this PR and see if it works for your use-case?
#83

from firestore-jest-mock.

@sbatson5 Looks like a great solution that will solve for my usecase.

from firestore-jest-mock.