Ours contain logic like that too. It’s unfortunate, but I rationalize it as:
Conversation
Consumers of the view model (views, basically) should be agnostic as to whether a particular transformation is stateful.
2
I'm not worried about the transformations; I'm worried about the event handlers. :/
1
Event handlers are just another form of input. View models transform all of these inputs into data for presentation.
2
Sometimes they transform those inputs into data; sometimes they perform I/O.
1
Everything Is A Signal™
2
2
I… I don't think that's helpful in this discussion. ;)
1
I think it’s relevant, because it parallels some other conversations that we’ve had. We use signals to encapsulate effects.
1
It bucks the conventional understanding of how signals might be used, but it means that we don’t need this distinction.
1
Our view models are a collection of inputs and outputs. Some of which are effectful. All of which are signals.
1
Replying to
What does it mean for an output to be effectful?
Replying to
e.g., resulting in the presentation of a new view controller, or the view model beginning a network request.
1
OK. How do you express those effects as outputs in the interface?
1
Show replies