-
Notifications
You must be signed in to change notification settings - Fork 948
Tree-shakeable FirestoreClient #3492
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
Conversation
💥 No ChangesetLatest commit: 9890082 Merging this PR will not cause any packages to be released. If these changes should not cause updates to packages in this repo, this is fine 🙂 If these changes should be published to npm, you need to add a changeset. This PR includes no changesetsWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Click here to learn what changesets are, and how to add one. Click here if you're a maintainer who wants to add a changeset to this PR |
Binary Size ReportAffected SDKs
Test Logs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, pending one comment that I left.
enabled: boolean | ||
): Promise<void> { | ||
return asyncQueue.enqueue(() => { | ||
persistence.setNetworkEnabled(true); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should persistence.setNetworkEnabled(true)
be invoked with enabled
instead of hardcodingtrue
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should not. It must! Thanks for catching.
4a93ee3
to
3e4c610
Compare
This extracts all logic from FirestoreClient into free standing functions. The goal of this is to no longer use firestore-exp in the tree-shakeable client.