-
-
Notifications
You must be signed in to change notification settings - Fork 344
Support Firestore #131
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
Comments
We'll see if I need to create another package, I hope I don't :) |
I don't see any references to it being deprecated. Where is it stated that the realtime database is going away? |
No, it's not deprecated. Firestore is in beta |
They are 2 separate products, firebase real-time database is not going away. |
and
They don't say anything about future improvements of the Realtime Database. It's dead. For me there is a high probability for the Realtime Database to be shut down within a couple of years. I hope not, but I think so. |
They said in the hacker news story (https://news.ycombinator.com/item?id=15393396) that they are separate products for separate use cases and that they will support both. |
Thanks for the link @ssijak
|
Along with improved querying, the offline capabilities for javascript SDK for firestore seems at first sight the most significant change to implement (although the interest of offline for a web app doesn't strike as key at first sight, the instantaneous response of the cache is good for fluid UI updates). |
Firebase real-time database already works nicely when disconnected |
From a few of the interviews circulating the web, it does seem like Firestore will become the "preferred" database for new users. There's no mention of Real-Time DB deprecation, but the emphasis is clearly shifting to Firestore going forward. |
@neovive That's pretty clear just from the link in the first post. Here's the relevant bit.
That tone seems to indicate that once cloud firestore is out of beta, they'll be recommending it for all new projects. |
can't wait for a firestore support |
Hey everyone! I've started using Firestore recently and I can't wait for vuefire to have support on this amazing product. I've seen not so many changes have to be done. Maybe it's useful to have separated fields on a component to support both: ...
firebase: {
myCollection: db.ref('/my-collection'),
},
firestore: {
myCollection: db.ref('/my-firestore-collection'),
},
... Is there anybody willing to implement it? |
Actually the Firebase ecosystem is (will be) using Firestore as its prefered database, the other "legacy" database being the Real Time Database (RTDB). So as Firebase is no more mainly a database but rather a collection of tools (whatever database, auth, hosting, etc.), maybe we should use the following notation: ...
rtdb: {
myCollection: db.ref('/my-rtdb-collection'),
},
firestore: {
myCollection: db.ref('/my-firestore-collection'),
},
... |
And while waiting for Vuefire to support Firestore the native solution is less convenient but quite easy: |
Yes, it's as simple as before, didn't took me long to get something working but I found a bug that I reported, so I'm holding back a bit for the moment. |
@posva +1 for different versions. |
+2 for different versions. |
IMHO it isn't upward compatibility completely. But all in all, we can think it is a successor. |
@Yatima-Kagurazaka It's nice you found a temporary solution but please don't promote it here. Right now I cannot code much for personal reasons, but I'll publish an official version as soon as I can |
I'm sorry. |
What's the update for firestore on vuefire? ;) |
I'll get an alpha release in the coming weeks with the basics features and probably a stable version with the full set before 2018 Sorry for not getting it done sooner but I was just super busy with personal matters and I'm still not at full capacity 😄 |
Closing in favour of #145 |
Breaking (pun intended) news: https://firebase.google.com/docs/firestore/rtdb-vs-firestore
Looks like a vuefire fork is needed…
The text was updated successfully, but these errors were encountered: