A modern programming language that makes developers happier.

kotlinlang

How do you sync a SwiftUI TextField with your Kotlin ViewModel using MutableStateFlow?

The textfield requires a Binding, either via a @Published var in a Swift ObservableObject, or via `init(get: , set: )`. The latter requires no additional variable, but it causes `Binding&lt;String&gt; action tried to update multiple times per frame.`

I just dont want to create another Swift ViewModel, because I already have a Kotlin ViewModel with Flows

Touchlab's KaMPKit has an example of sharing ViewModels. I'm not sure if it will meet your use case, but it would be a place to start.

<https://github.com/touchlab/KaMPKit|https://github.com/touchlab/KaMPKit>

moko-mvvm `declarative-ui` branch contains example of integration kotlin viewmodel directly in swiftui without any additional swift viewmodels.

<https://github.com/icerockdev/moko-mvvm/blob/6a1d9da18b6650c9f364a0f72a8614fa906a596c/sample-apps/iosApp/iosApp/BookListViewBinding.swift#L19>
here utils for this implementation - <https://github.com/icerockdev/moko-mvvm/blob/6a1d9da18b6650c9f364a0f72a8614fa906a596c/sample-apps/iosApp/iosApp/mokoMvvmExt.swift>

<@UC44UESH4> So you do use Bindings.init(get, set) too. At least with MutableStateFlow instead, I get the warning `Binding&lt;String&gt; action tried to update multiple times per frame.` and it does not always update the state :thinking_face:

<https://github.com/icerockdev/moko-mvvm/blob/6a1d9da18b6650c9f364a0f72a8614fa906a596c/sample-apps/iosApp/iosApp/mokoMvvmExt.swift#L119> here updates magic

<@UC44UESH4> Thanks.
I’m curios, what do you think about simple fire `objectWillChange.send` right in the setter of the binding?
```func binding&lt;T&gt;(_ keyPath: KeyPath&lt;Counter, MutableStateFlow&gt;, t: T.Type) -&gt; Binding&lt;T&gt; where T: Equatable {
        binding(flow: self[keyPath: keyPath], t: t)
    }
    
    func binding&lt;T&gt;(flow: MutableStateFlow, t: T.Type) -&gt; Binding&lt;T&gt; where T: Equatable {
        .init(get: {
            flow.value as! T
        }, set: { new in
            if (new != flow.value as! T) {
                self.objectWillChange.send()
                flow.setValue(new)
            }
        })
    }```

because flow can be change itself. in your case you will emit data to flow, but not read this flow