Hey guys, I've got a question about the internals of Orbit, why is the `intent` function using `runB...

# orbit-mvi

[Benoît]

Hey guys, I've got a question about the internals of Orbit, why is the intent function using runBlocking? What's the point of using a CoroutineScope when creating the ContainerHost like so scope.container(...)?

[Mikolaj Leszczynski]

runBlocking is there just to deliver the intent to the container channel’s buffer. We could replace it with something else really.

The container is scoped according to the CoroutineScope - so if the CoroutineScope is cancelled, all in progress intents are cancelled as well.

[Mikolaj Leszczynski]

If you’re using an Android ViewModel - it uses the ViewModel’s CoroutineScope.

[Mikolaj Leszczynski]

it kind of happens under the hood there

[Mikolaj Leszczynski]

let me know if you need more info @Benoît

[Benoît]

Thanks for the info.
I'm not using Android ViewModel because I'm doing a KMM project, but passing the scope isn't an issue anyways.

And what's the difference between the scope used in scope.container() and the one passed in Container.Settings(intentDispatcher = ...) ?

[Mikolaj Leszczynski]

Dispatcher != Scope 🙂

[Mikolaj Leszczynski]

the dispatcher in the settings is there if you wanted to change the dispatcher the incoming intents are handled on.

[Mikolaj Leszczynski]

to be honest this is there mostly for unit testing

[Mikolaj Leszczynski]

I don’t see why you’d want to touch that outside of that use case

[Benoît]

Yeah sorry my question was confusing 😅 a scope "contains" a dispatcher, is it ignored then?

[Benoît]

Yep unit testing is exactly why I wanna know more about this 🙂

[Mikolaj Leszczynski]

internally we do private val scope = parentScope + settings.intentDispatcher

[Benoît]

aaah yeah that's what I needed to know!

[Benoît]

Thanks a lot 😄

[Mikolaj Leszczynski]

no probs