But I'm still really confused about what I should ...

# arrow

[bjonnh]

But I'm still really confused about what I should do when executeQuery throw an exception

[raulraja]

What would be the acceptable behavior?

[raulraja]

An exception is always encapsulated by IO

[bjonnh]

testclass.query("Test").unsafeRunSync {
result ->
result.fold({ println("Error") }, { println(it) })
}

[bjonnh]

I tried that, but it failed inferring the type

[raulraja]

unsafeRunSync will always throw the exception

[bjonnh]

facepalm I wanted unsafeRunAsync here

[bjonnh]

thanks

[raulraja]

you should either call attempt before unsaferunAsync which will give you a Either<Throwable, A> or have your return type in query return an IO<Either<Throwable, A>> and keep on composing programs before you run it.

[raulraja]

If an app has more than one unsafeRun it's always indication of bad composition

[bjonnh]

for now I'm spreading Arrow things slowly… It is a JavaFX app so I'm not ready to move everything into that

[raulraja]

What I ment to say is that instead of attempt + unsafeRun

[raulraja]

you can just call handleError or handleErrorWith

[raulraja]

wich will return another IO and it's just like map/flatMap but over the Throwable