```val searchQuery = state.getLiveData("query", "") private val tasksFlow = combine( search...

# announcements

[Florian]

val searchQuery = state.getLiveData("query", "")

private val tasksFlow = combine(
        searchQuery.asFlow(),
        preferencesFlow
    ) { query: String, filterPreferences: FilterPreferences ->
        Pair(query, filterPreferences)
    }.flatMapLatest { (query, filterPreferences) ->
        taskDao.getTasks(query, filterPreferences.sortOrder, filterPreferences.hideCompleted)
    }

If I set searchQuery.value = null this will crash. How can I get null-safety here?

[Adam Powell]

Declare your LiveData with a nullable type if you're going to assign null to it

[Florian]

I don't want to assign null to it

[Florian]

LiveData is nullable by default right

[Adam Powell]

Yes, LiveData is always nullable, but its observers are declared without nullability annotations

[Florian]

it doesn't seem to change anything

[Florian]

The type stays String!, I don't get a compiler warning and asFlow can still crash