This may be a better issue for Ember Concurrency itself (as I suspect this request would require some plumbing there given neither TaskInstance nor TaskProperty are public API), but since it's in the vein of decorators, I thought I'd start here.
While we have support for Encapsulated Tasks with Decorators (this PR), the "encapsulated object" itself is not a class I can add decorators to.
Let's say I have a "countdown" task that I reuse in a bunch of different components in my app. In the old non-class-based decorator world, I might write this utility like so:
This may be a better issue for Ember Concurrency itself (as I suspect this request would require some plumbing there given neither
TaskInstance
norTaskProperty
are public API), but since it's in the vein of decorators, I thought I'd start here.While we have support for Encapsulated Tasks with Decorators (this PR), the "encapsulated object" itself is not a class I can add decorators to.
Let's say I have a "countdown" task that I reuse in a bunch of different components in my app. In the old non-class-based decorator world, I might write this utility like so:
But, in the world of Classes & Decorators, it might be nice to express this with all the modern goodies. Perhaps it'd look something like:
(Let me know if I should move this issue — and happy to contribute to making this happen if it makes sense)