Eduardo San Martin Morote
Eduardo San Martin Morote
@SumNeuron yes, you still need to do that
You can create a computed that generates the object from the array. More information would be helpful to decide whether this feature is worth adding or not 🙂
I don't have plans right now to add it but it would make sense for Vue 3. Good news is, as you found out, the core is ready for this...
Yeah, we should definitely allow a way of passing https://firebase.google.com/docs/reference/js/firebase.firestore.SnapshotListenOptions, probably as a whole option named `snapshotListenOptions` even though I would really like to do it like you suggested: merging...
Right now this should be possible by awaiting a bind and then unbinding it. For Firestore, this benefits from fetching references. Maybe this could be added as a standalone function...
vuex-module-decorators not being an official library, I don't want to directly expose the decorator on vuefire, instead we could add a page to the cookbook docs explaining how to do
Right now, you need to use something as ``this.$bindAsObject(`contacts_${key}`)``. Handling deep paths (`my.nested.array.0.property`) may be supported in future releases
$bindAsObject doesn't exist anymore, it's automatic (more in the docs 🙂 )
Following the tip at the top should allow anybody to do a PR: https://v1.vuepress.vuejs.org/plugin/official/plugin-pwa.html
I'm not sure if there is a way to also type the methods and other properties. Maybe using the type of a method in a Vue instance we can infer...