emmano

Thanks a lot for the time you have put into this. We have leveraged [onRetainCustomNonConfigurationInstance()](https://developer.android.com/reference/android/support/v4/app/FragmentActivity.html#onRetainCustomNonConfigurationInstance())/[getLastCustomNonConfigurationInstance()](https://developer.android.com/reference/android/support/v4/app/FragmentActivity.html#getLastCustomNonConfigurationInstance()) retain/retrieve the `@PerActivity`(or more accurately "PerScreen") scoped component (Dagger) that holds the dependencies for the...

You are correct. My comment was regarding how to retain scoped dependencies. To solve the issue of `view` being `null` during config changes you can probably make the data layer...

Loaders use the mechanism that I described above.

Any updates on this? We are also trying to move off jCenter.

> About this issue you mention, this feature could be helpful for the renderers implementation invoking findViewById() inside the render method, but not for most of the implementations using this...

Sure. The first one should be simple. The second one will take more time. I am also looking into issue #45.

So, it looks like in order to get this to work (without library changes) the following needs to happen. Renderers will have to take a `View`(the root `View`) in their...

> The second step is sending the PR. We need to create the Kotlin module. Implement the feature. Configure the module to be deployed to maven central as the root...

>Besides, with the new API change we wouldn't need the layout inflater no more and we'd be requiring renderer constructor to know how to build views. Yeah, I did not...

I see. Thanks a lot for the detailed response!