Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgraded to Firestore 0.15.4 #309

Merged
merged 2 commits into from
Jul 20, 2018
Merged

Upgraded to Firestore 0.15.4 #309

merged 2 commits into from
Jul 20, 2018

Conversation

hiranya911
Copy link
Contributor

  • Re-exporting the Firestore Timestamp type
  • Updating affected tests

Copy link
Contributor

@schmidt-sebastian schmidt-sebastian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

There's a lot of churn in the package-lock.json though, when only one version should have changed.

@@ -76,7 +78,7 @@ describe('admin.firestore', () => {
.then((snapshot) => {
const data = snapshot.data();
expect(data.timestamp).is.not.null;
expect(data.timestamp instanceof Date).is.true;
expect(data.timestamp instanceof admin.firestore.Timestamp).is.true;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is: expect(data.timestamp).to.be.instanceOf(admin.firestore.Timestamp)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

I believe the package-lock.json changes are because we define a lot of our dependencies loosely with wildcards. So everytime we regen the file, there are new versions to pick up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants