<https://developer.android.com/topic/libraries/vie...

# android

[itnoles]

https://developer.android.com/topic/libraries/view-binding#fragments o.O

[wasyl]

What is surprising here?

[Paul Woitaschek]

Nullability annotations in kotlin code suprised me. And overrite annotations but no override keyword too 😛

[Paul Woitaschek]

And the missing type of the binding maybe too

[itnoles]

No lateinit too

[wasyl]

Oh, I focused on the binding being there 😄 Right, seems like a poor example there 😕

[Paul Woitaschek]

Why lateinit? @itnoles

[itnoles]

Make sure binding get called and available by times I needed it

[Luke Sleeman]

🤔 I belive there is a way to open up a issue against the android documentation. Perhaps somebody should re-write it with more idiomatic Kotlin code and submit an issue for them to fix it.

As it is right now, new developers will learn bad practises by copying googles code.

[Paul Woitaschek]

At least it won't compile

[Paul Woitaschek]

@itnoles You don't need a lateinit there, that's why they introduced a backing property so you can acutally null it and remove the reference to the view tree

[Dustin Lam]

Thanks for mentioning this, by the way - best way to get visibility on issues is through the issue tracker https://source.android.com/setup/contribute/report-bugs#filing-a-bug

[Tim Malseed]

@itnoles lateinit here would defeat the purpose - you can’r set a lateinit property to null, so you wouldn’t be able to release the reference to the binder in onDestroyView()

[itnoles]

I guess best way is https://github.com/android/architecture-components-samples/blob/master/GithubBrowserSample/app/src/main/java/com/android/example/github/util/AutoClearedValue.kt#L31

[Tim Malseed]

Great, exactly what I was after