Feature Request P2
Status Update
No update yet.
Comments
il...@google.com
jb...@google.com
Just FYI, yeah it is strong guarantee that was specially designed this way. I keep it open as request to improve documentation
lb...@gmail.com
Would this workaround be good:
@Suppress("UNCHECKED_CAST")
class MutableLiveData2<T>(value: T) : LiveData<T>(value) {
override fun getValue(): T = super.getValue() as T
public override fun setValue(value: T) = super.setValue(value)
public override fun postValue(value: T) = super.postValue(value)
}
?
Source:
Description
Currently we have to rely on Lint to enforce null safety of
MutableLiveData. However, we would like to have compile-time safety. Sometimes we want to completely forbid null values from being submitted toLiveDataor emitten from it. And sometimes we want the opposite. This feels like a job for Kotlin nullable and non-null types.However, the nature of
LiveDatamay make this tricky, since most of the times it's created without an initial value.lateinit varmay be used, but what shouldgetValue()return when it's initial value isn't set and type parameter is non-null?