This repository was archived by the owner on May 19, 2025. It is now read-only.
Prepare Firestore functionality#273
Merged
tjmonsi merged 2 commits intoFirebaseExtended:masterfrom Oct 4, 2017
Merged
Conversation
Contributor
|
@mbleigh and I are working on the firestore component (or mixin). Will be working on it next week. But thanks for this. |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Preliminary changes necessary to enable Firestore functionalities.
For now this will only allow to initalize
<firebase-app>with the necessaryprojectIdin the options and loads the script necessary to usefirebase.firestore.How best to implement
firebase-firestore-queryandfirebase-firestore-documentremains to be seen.And I guess the firestore persistance option should be added to
firebase-app?