Handling errors with coroutines seem convoluted. !.

• architecture-components-samples

  26 23,268 2.3 Kotlin

  Samples for Android Architecture Components.

  

Hey guys, Im trying to recognise more about api calls in a contemporary architecture. I am using retrofit with livedata/coroutines to make my api calls, but I'm struggling with error handling. Most of the solutions I find, even in googles own example, includes writing a wrapper around your api request and handle the error that. It seems overly complicated and frankly stupid to do something like that for, what I consider at least, rudimentary functionality. Even with Dart/Flutter, google has made this easy ‏‏‎ with async/await and Futures. Am I being lazy to think that if even google needs to write extra code to solve a common use case, they should probably add it to the framework? I dont know, maybe I just needed venting.. what do you think? google's project: https://github.com/android/architecture-components-samples/tree/master/GithubBrowserSample

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project