Are there any best practices/designs you follow wh...
# android
k
Are there any best practices/designs you follow while handling API errors when using retrofit with Coroutines? I'm currently following this article to handle errors as states using sealed classes but I'm not sure how should I deal with mapping those errors with string resources so that I could support them in multiple languages. Also, error responses with multiple json formats is yet another challenge for me. Any links to articles you'd recommend or a brief idea would also work. Thanks!
j
You can map from network to domain, the problem is the context you use to get the android strings and if you use ViewModel, you can have problems when you rotate the screen
k
Thanks!
c
I think slack has something for this?
k
Great! Thanks