Firestore Roadmap

[posva]

It's time for vuefire to update to Cloud Firestore 🎉

In order to give you some visibility about the new version, here's a checklist with features. Feel free to ask about new things, I'll probably forget to add every single feature to the list.

Until the version becomes stable there may be breaking changes, but if you're using the current version of vuefire, don't worry, it won't affect you. The new version will be published under the next tag on npm, meaning that you can already play with it if you want

Firestore is now supported by the latest tag

Keep in mind, there're still no docs but you can check the exapmles/ folder and tests for inspiration

Features

• Document binding
• Collection binding
• unbind on destroy
• Manual bind
• Manual unbind
• Support firestore as a function
• bind -> returns a promise
• option to remove data right away when binding on top of an already bound ref
• Automatic unbind when already bound
• Development warnings
• Recursive ref binding + unbinding
  • Bind refs in documents
    • bind refs inside of objects
    • bind refs inside of arrays
    • bind plain refs
  • Stop at 1st depth by default
  • allow passing max depth
• customizing id key used
• Move tests to Jest
• Split code to have both, vuefire and vuexfire code here
• Allow users to use both RTDB and Firestore at the same time
• Documentation
  • Vuepress site
  • Live Examples
  • Figure out a way to document common things between vuefire /vuexfire
  • Vuexfire
    • Good practices about binding documents and collections
    • Where to host references to collections and others (Make it easy to access the per item firebase refs. #180)
  • Cookbook
    • Pagination
    • How to write tests
    • Using without a bundler (prototyping)
      • Add full template to use
    • Using with Typescript
    • Dynamically bound properties (Vue.set)
  • Note in getting started about docs being for people using webpack (or project with cli
  • Link to cookbook

If you find bugs, please, open a new issue (but make sure to check if it hasn't been fixed already 😛 )
if you want to check the ongoing work, it's on the firestore branch

[posva]

Small update: Things are working really well, I just released an alpha version. The reason is taking so much time is because there's a lot of edge cases for refs (embed documents into other documents) to handle 😆
Most things are working but if you find bugs, please open an issue with a repro, it would really help!
For instance, I yet have to fix a bug when updating a document referenced in an array on a bound document that makes the update delay fixed in latest release

[taylorhoward92]

Thanks for your hard work in supporting Firestore. When binding to a collection, is there a way to get the ID or ref of each document within the collection?

[posva]

it's the key id attribute. It's non-enumerable, so it doesn't appear when copying the object

[taylorhoward92]

Thanks. I was using a collection with v-for on a component and binding to the object instead of binding on each property. This meant that the id prop in the component could not be found.

Specifying a property for the id did the trick:
<ListingItem v-for="listing in listings" :key="listing.id" v-bind="listing" :id="listing.id"/>

[posva]

sorry, I meant id 😆

[WillieCubed]

I have a concern with this:

If you are looking for Firebase realtime support, install v1 instead: npm i vuefire@v1

Does this mean VueFire is dropping support for Firebase RTDB? It's still functional and doesn't appear to be going away any time soon. Cloud Firestore isn't purely an upgrade to RTDB - it's a sidegrade with its own strengths and weaknesses. RTDB is great for getting JSON data easily synced between clients, and I don't want to see VueFire lose that featureset.

[posva]

No, don't worry, the realtime db will still be supported and receive bug fixes and even feature requests in vuefire v1. I will probably spend more time working on v2 (Firestore) because it's funnier and you know, it's all on my free time 😄, but both versions will be supported for some time. That being said, there's not much to add to vuefire except for already opened issues and PR.
The readme of the Firestore branch is prepared for release, that's why it tells you to install vuefire@1 but you can still do vuefire

[eeerrrttty]

ok, something important... i can install vuefire@next AND USE FIREBASE ON IT? im making a new app that will be REALLY BIG, and im making it using vuefire, i want to use the lattest version so i can use firestore instead of firebase for better queries, so... that said, can i use vuefire@next to use both firebase and firestore?