I’m clearly missing something simple here what wou...
# coroutines
l
I’m clearly missing something simple here what would be the idiomatic or right way to map and propagate an error using coroutines? let’s say I have my repository and I want to remap a Http 400 exception to a domain exception, so if I
runCatching/try
here the exception would be swallowed and not be caught on the try catch of the view model right? What I could use in this case? Would
runCatching{}.recover{}
work on this case?