@machty On this post: So have you tried ember-concurrency yet? you stated:
Never write an if(this.isDestroyed) check ever again 1 → instead, use a Task, which gets automatically canceled when the object it lives on is destroyed
I’m not sure that’s completely fair. If I understand right, tasks are essentially decorators? You can’t use them anonymously, right? If that’s true, you’d have to create a class function for every promise handler (resolve/reject/finally) right?
Maybe there is a way to make it work that I’m not seeing. Given the first code snippet in my original question, how would you modify that to use a task so I didn’t have to check isDestroyed?