Benjamin Fox

Thanks, I do rather like the way this babel plugin turned out. (That said, I would just point out that it's not really much more than a weekend project I...

Yes, I see. `vue-async-computed` predates the `errorCaptured` error handling mechanism in Vue, so that's why it has it's own different error handling. But now that Vue has this robust error...

I agree, but for now I'm treating `vue-async-computed-decorator` as something of a beta release. I want to give it a few days or maybe a week or two to iron...

I'm not quite sure how it is an improvement to specify the default in `data`. What makes you prefer this proposed method for defining defaults for your async computed properties?

I see. I suppose it is worth having some consistency with `vue-apollo` and `vuefire`, and if they do it this way, it's probably worth having the ability to do the...

Hey, I've added a test case that tries to test this issue, but I'm not managing to reproduce it. Can you take a look, and help me track down what's...

Neither of those should matter (especially since the default `default` is already `null`.) I've run a variant of the test with a 1-second long timeout and an explicit `default: null`,...

I see what you're saying, and I've tried to replicate exactly that in the test suite here: https://github.com/foxbenjaminfox/vue-async-computed/blob/3be0d8590bf772bf05c86845347e63318438f9ab/test/index.js#L1017-L1050 The test still passes just fine, so I doubt that the problem...

You're quite right that this might be a bit confusing. Ultimately, it's a pretty standard beginners stumbling block with callbacks. Many beginners often try to write something like: ````js try...

@Yovar: That's fine. I'll try and think of how I can best write it up myself. Thank you for raising this issue, in any case. @dsl101: As @Yovar says, the...