Question: What is a proper way to deal with OpenFileDialog etc?

Currently I use something like this:

Button.create [
    Button.content "Some text"

    Button.onClick (fun _ ->
        let ctx = System.Threading.SynchronizationContext()
        async {
            let ofd = OpenFolderDialog()
            let window = getWindow()
            let! path = 
                ofd.ShowAsync(window) 
                |> Async.AwaitTask
            do! Async.SwitchToContext ctx
            path
            |> Msgs.SomeMsg
            |> dispatch
        } |> Async.Start
    )
]

but I’m not sure whether this is a good approach or not.

[AngelMunoz]

I see, yeah I agree it could couple you to a specific implementation But you can always fallback to use an interface instead of a concrete class (like my example) to make it agnostic to your update function

let update  (msg : Msg) (state: State) (dialogService: IMyDialogService) = 
       match msg with 
       |  OpenWindow ->
            state, Cmd.ofAsync.either dialogService.OpenFolderDialog () OpenFolderSuccess OpenFolderError
       | OpenFolderSuccess path -> { state with path = path }, Cmd.none
       | OpenFolderError ex -> { state with error = Some ex.Message }, Cmd.none

inside the Window constructor, you should be able to get the service you need without worrying about coupling your MVU to your platform

[FoggyFinder]

you can also pass the window as part of the update function and use the Elmish Cmd.ofAsync.* commands

I suppose this approach breaks MVU pattern ? I expect that update function/part will be totally independent from View side.

I.e. in case if I later decide to use Fabulous or Elmish.WPF or anything else then I can switch to it easily. Well, at least in theory.

Buf if I pass Window to the update function then I will be sticked to Avalonia.

Though, this is the first time I use Elmish for my app so I might be wrong 😃