I know the idea of a DI container scares a lot of people though! I like it as a declarative approach personally
Conversation
Oh, no, I like that too. I just wouldn’t override UIStoryboard to do it—too dangerous. That thing’s coupled all over the place.
2
I know I know..just don’t use storyboards
2
has-a, not is-a, so you stay in control.
2
so I guess you wouldn’t trigger segues to drive navigation from the content view controllers?
1
Good question. Not sure how to handle that gracefully without subclassing.
1
I’ve been thinking about these challenges for quite a while - I really do like hearing different perspectives!
1
Replying to
I’d probably avoid all the string typing. Have the VC expose addRequestSignal; the wireframe would subscribe and react.
Replying to
sure - that’s where the event handling code ends up instead of the view model, like you mentioned on the talk
Replying to
once you move away from invoking segues though, why use a storyboard at all?
1
You tell me. :)
1
Show replies