I'm working on a retrofit `CallAdapter` that would work with: ```interface Service { @GET("/")...

# arrow-contributors

[stojan]

I'm working on a retrofit CallAdapter that would work with:

interface Service {

    @GET("/")
    suspend fun bodyEither(): Either<String, String>

    @GET("/")
    suspend fun bodyResponseE(): ResponseE<String, String>
}

// a more FP/Kotlin friendly version of retrofit2.Response
data class ResponseE<E, A>(
    val raw: okhttp3.Response,
    val code: Int,
    val message: String?,
    val headers: Headers,
    val body: Either<E, A>
) {

    val isSuccessful: Boolean = raw.isSuccessful
}

where the you can put the error body on the left. Would that be a good fit for arrow-integrations ?

[raulraja]

this would be great o have in the arrow retrofit integration as an addon or improvement of that is in there

[raulraja]

thanks @stojan arrow 💌

[HarryPulvirenti]

This remember me something right @stojan?🤔 🧌

[stojan]

https://github.com/arrow-kt/arrow-integrations/pull/26

[Hiosdra]

If there is some optimism about suspend + Either, what would you say if I will write somthing similar, but for IO?

@GET("/")
fun getUser(): IO<E, T>

Where T will be the same as T in:

fun getUser(): Mono<T>

And E will be ??? Maybe retrofit’s HttpException?

[stojan]

why not 🙂

[stojan]

maybe we can generalise on top of some typeclass

[Hiosdra]

ok, I will explore that topic 😉

[raulraja]

we can make Mono support E

[raulraja]

for now slapping over it EitherT

[raulraja]

but @simon.vergauwen has better ideas for long term solutions