These questions are hard to discuss in the abstract. That Can Be Represented, but It Depends On What The Request Is.
Conversation
Sure. Broadly, my concern is that the approach you suggest will lead to lots of stateful effects living in the view model.
1
Yes—in many ways, that’s the point.
3
e.g. a presentation-oriented transformation of a model value to some view-appropriate value.
1
Ours contain logic like that too. It’s unfortunate, but I rationalize it as:
1
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
Replying to
I… I don't think that's helpful in this discussion. ;)
Replying to
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
Show replies