wujekbogdan
wujekbogdan
@kamikazePT Thanks for the fork. I have an idea on how to make it more flexible. Instead of having 2 version of the plugin: one for `dotenv` and one for...
> What makes you prefer this proposed method for defining defaults for your async computed properties? There are 2 reasons: 1. It's more Vue-way. 2. All the defaults (async and...
> vue-apollo does the same thing, data() serves as the placeholder until results from the server are in. Same in [vuefire](https://github.com/vuejs/vuefire). That's why I said it's kind of a vue-way.
I can't use the plugin for *.less files. I can see "Rearrange code" option in the Code menu, but it's grayed out.
Is `vuefire` discontinued? We're going to migrate to our application from Vuex to Pinia and I'm not sure what's the best way to implement Firestore bindings. Shall I use `vuefire@next`...
We're still using Vuex in that project where we planned Pinia migration, but If I were to choose a solution I would probably go for `@vueuse/firebase` as it's the only...
@jagretz Thanks, I'll check it out.
It would be great if there was a `queue.onError` method. **// Edit** And even better if `onError` and `onSuccess` callback were called with a context of a specific task, but...
Ignore my previous post `onSucces` and `onError` callbacks and the metadata features are not needed. Here's the solution: ``` typescript public async processQueue() { const cronTasks = await this.getCronTasks(); const...