Mark Dubkov

Split mvvm-state into components for working with livedata and with flow: mvvm-state-core, mvvm-state-livedata and mvvm-state-flow

iOS nullable value from CStateFlow

1

[mokoMvvmFramework](https://github.com/icerockdev/moko-mvvm/blob/e6023df467cd297ea20f5764b612535929e87a49/mvvm-flow/apple/xcode/mokoMvvmFlowSwiftUI/ViewModelState.swift#L32) does not allow to get a iOS nullable value from CStateFlow, , it is necessary to add at the moment, force unwrap is being used there ``` func stateNullable(...

``` class MutableStateAdapter( private val state: State, private val mutate: (T) -> Unit ) : MutableState { override var value: T get() = state.value set(value) { mutate(value) } override fun...

Bug ``` sealed interface FeedListUnit data class AddPostUnit( val onClick: () -> Unit ): FeedListUnit data class FeedUnit( val dateTimeString: StringDesc, val postText: String, val likesCount: Int, val dislikeCount: Int,...

localization of unicode characters

3

string.xml in shared module: `\uD83D\uDE00` generate in androidMain multiplatform-strings.xml `\uD83D\uDE00` generate in Localizable.string file from iOS framework `\uD83D\uDE00` when calling the `localize()` function from iOS, the string `uD83DuDE00` is returned...

add the ability to state the current value for a specific view, and not on the view in which the StateObject/ObservedObject for the ViewModel was created here is an example:...