Fixed a fragment view leak by using DataBinding-ktx

[TomoyaShibata]

Issue

• close Fix fragment view leaks #153

Overview (Required)

• References to view remain unintentionally when add a fragment to a backstack.
• You can destroy the reference by setting binding = null in Fragment#onDestroyView lifecycle, but introduced wada811/DataBinding-ktx which does it automatically.

Links

• https://github.com/wada811/DataBinding-ktx
• https://twitter.com/Piwai/status/1201686009349455872

[takahirom]

👀

[takahirom]

DataBinding-ktx is awesome🔥
But if we want to use like recyclerview adapter. We should assign null
How about this?
https://github.com/android/architecture-components-samples/blob/9826b59956eb93c9e627bdf16a19a1c8bc28ce14/GithubBrowserSample/app/src/main/java/com/android/example/github/util/AutoClearedValue.kt#L31-L40
I think it is OK to use DataBinding-ktx , but I am thinking.🤔

[TomoyaShibata]

AutoClearedValue awsome idea too! I will try it's approach.

If you adopt AutoClearedValue approach, do you want to unify it to AutoClearedValue?

Another great feature of DataBinding-ktx is the automatic invocation of setLifecycleOwner, but this is not required for this app. So it is possible to unify to AutoClearedValue.

[TomoyaShibata]

Add what you care about. 📝

There are comments in the source code that can create situations that cause NPE to be thrown, and This tweet is have mentioned it. 👀

https://twitter.com/wada811/status/1217361894224220160

[takahirom]

Thank you for investigate 🙏
If you have time, can you create AutoClearedValue version PR?
I don't think it's a big problem. 🙇