Post #2625583
2026-04-30 17:29 UTC
@mattiem@mastodon.social The specific case I have in mind is a UIView or UIViewController spinning up the task and calling an async method on a view-model/interactor of some kind. So it does feel like an AsyncButton scenario in spirit.
In my mind I want the equivalent of the task modifier in UIKit.
Replies (1)
-
@blagdon@techhub.social 2026-04-30 17:37
@sjs@techhub.social @mattiem@mastodon.social I think a good way to think about this might be whether you still want the side effect to happen regardless of whether the button still exists. Imagine tapping the button writes something to the local data store, or performs a network request. If the button gets destroyed before the work completes we typically don’t want to abandon the work, so fire and forget in that case makes sense.