threading and using different dispatchers for Stor...

# store

[André Thiele]

threading and using different dispatchers for Store:
i see that store uses DefaultDispatcher by default, even when using .stream().flowOn(ioDispatcher)
how can i change that so that all remote calls from my fetcher are part of ioDispatcher? should i move withContext(ioDispatcher) to fetcher? i would like to keep all dispatchers in Repository layer which is using .flowOn with store at the moment because we have multiple repository implementations, i don't want to add dispatchers everywhere. i dont see any info in the docs on this @Matthew Ramotar

[André Thiele]

i actually noticed that this is default behaviour https://stackoverflow.com/questions/78502056/why-thread-name-is-defaultdispatcher-worker-even-though-i-specify-function-to-ru

[André Thiele]

do i still need to reference my dispatcher in flowOn() or is it not necessary?

[Matthew Ramotar]

If you want to verify the dispatcher, you can do

Fetcher.of { key ->

  // DON'T ACTUALLY DO THIS IN PROD
  val interceptor = coroutineContext[ContinuationInterceptor]
  check(interceptor == ioDispatcher) { "Fetcher not on IO" }

  api.get(key)
}

https://discuss.kotlinlang.org/t/checking-that-a-coroutinescope-uses-the-correct-dispatcher/23386

[Matthew Ramotar]

.flowOn(ioDispatcher) is the right mechanism so you don’t need to scatter withContext(ioDispatcher)