Add DI framework as dependency - Part 2 #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use the DependencyContainer framework to inject containers in the routers which will be responsible for instantiating the whole flow of the app. The Graph's container should register and resolve all dependencies of the app. In order to do it the container must be passed down to every Router. No other classes besides Routers should have access to it. Routers are the only responsible for instantiating new screens and they are in charge of injecting all necessary dependencies into them.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use the
DependencyContainerframework to inject containers in the routers which will be responsible for instantiating the whole flow of the app.The
Graph's container should register and resolve all dependencies of the app. In order to do it the container must be passed down to everyRouter.No other classes besides
Routersshould have access to it.Routersare the only responsible for instantiating new screens and they are in charge of injecting all necessary dependencies into them.This is pull request is related to the second part of a series of blog posts about Clean, Simple and Composable Routing for iOS Apps.