Hello. What’s best practice on how to handle errors for a multi-platform library that serves as an A...

# multiplatform

[Jeff]

Hello. What’s best practice on how to handle errors for a multi-platform library that serves as an API client?

Thoughts so far:

1. Expose suspend functions that return successful responses as data classes. These functions can throw errors.
2. Return kotlin.Result

[Pablichjenkov]

2 but I would prefer my own Result sealed class. That could be Success(data) and Error(ErrorInfo)/Error (Throwable)

[Kirill Zhukov]

we use https://github.com/michaelbull/kotlin-result

[Kirill Zhukov]

Arrow is another option https://arrow-kt.io/

[Kirill Zhukov]

kotlin.Result is kinda half baked, not too great… Plus runCatching: Result is bad for using with coroutines cause it swallows cancellation exceptions

[Jeff]

Which is better for this use case.. arrow or https://github.com/michaelbull/kotlin-result

[Jeff]

And can I provide both options to users.. the plain suspend funtions and the result implementation

[kqr]

or https://github.com/npryce/result4k ?

[Pablichjenkov]

Provide a basic api that serves only suspend functions or the use cases that fetch the network stuff and then provide(in a separate artifact), extra wrappers for the desired result library of customers choice. The problem with including a third party in the basic implementation is that your client might be using another Result library and will pollute their namespace