Is it okay to inject the same component context into every child component?

[plusmobileapps]

The samples in decompose seem to have a manual dependency injection system setup always using the ComponentContext provided by the router childFactory. I was curious if it's important to use that ComponentContext passed from this method, or if it would be okay to just register ComponentContext in a DI graph and use that when creating child components?

As I'm digging deeper into some of the source code at RouterEntryFactoryImpl, it seems like it might be important to actually make sure the ComponentContext from the childFactory method is being used since it is creating a new ComponentContext and MergedLifecycle?

[arkivanov]

Good question! It's very important to use individual contexts for each child, as mentioned in the docs (a warning at the end) - https://arkivanov.github.io/Decompose/component/overview/#adding-a-child-component-manually

[plusmobileapps]

Ahh, thanks missed that tiny warning. Made a small improvement to make this clearer to users when looking through docs #101