FakeFirestore doesn't declare FieldValue about firestore-jest-mock HOT 7 CLOSED

I think the error happend because FakeFirestore does't have the following fields implemented: FieldValue, arrayUnion, arrayRemove, increment, delete and FieldValue.serverTimestamp.
So when jest overides firestore this fields don't exists in FakeFirestore so the error is that FieldValue is undefined so it doesn't has serverTimestamp

from firestore-jest-mock.

Turns out that classes need the new keyword. We cannot use new firestore(), as the canonical syntax does not support this.

Solution: declare the firestore property as a named function, and set a static method inside its body! Like so:

firestore: function firestoreConstructor() {
  firestoreConstructor.FieldValue = FakeFirestore.FieldValue;  // The magic sauce
  return new FakeFirestore(overrides.database);
},

That seems to work in my testing, and Travis CI agrees. 😁

from firestore-jest-mock.

I've tried importing "firebase-admin" before "firestore-jest-mock" and calling mockFirebase, and set FieldValue on the new firestore instance, but that doesn't work at all the way I'd hoped it would 😅

from firestore-jest-mock.

To note how I use FieldValue, I use its arrayUnion, arrayRemove, increment, delete, and serverTimestamp functions. As for testing, I'm okay just checking the mock that they were called, since my code doesn't (or I suppose shouldn't) rely on or confirm updates made to the database in the same function.

from firestore-jest-mock.

I would love to start a PR and work on this myself, but I cannot seem to figure out how to get my Node package to install local packages. (I mean, it installs just fine and points to the right file, but my tests behave as though no mock was made, whereas when I use your package by name and version, the above behavior occurs to indicate that the mock was successful).

from firestore-jest-mock.

Okay, I've got an implementation that tests well so far. PR soon.

from firestore-jest-mock.

A bit of an issue in the firestore stub. If I'm reading it right, the firebase.firestore mock is implemented this way:

firestore() {
  return new FakeFirestore(overrides.database);
},

The canonical firestore.FieldValue is defined statically on the firestore type. I'm having a hard time finding examples online, but I'm not sure that JavaScript functions can have static properties defined on them.

I'm not finding many answers readily online. Would something like the following work?

firestore: class extends FakeFirestore {
  constructor() {
    super(overrides.database);
  }
},

The idea is to expose both the constructor and static methods, so would this work if I have the FieldValue class defined as a static property of FakeFirestore?

from firestore-jest-mock.