A modern programming language that makes developers happier.

kotlinlang

Hi folks, in which cases would you recommend to use <https://arrow-kt.io/learn/typed-errors/working-with-typed-errors/|arrow-kt typed errors> for a web application?
Context: in the web application I'm working on, almost every method on any layer (except DB layer) returns a Either, which forces us to map errors, or to use for comprehension.
This looks good in some cases, but when a method cannot throw an exception, it looks over-complicated
Are there you some cases where that helps / some other where it is too much?

I think the question is more suited for <#C5UPMM0A0|arrow>.

I also asked a very similar thing there a while back. Perhaps it contains at least some useful thought for you. <https://kotlinlang.slack.com/archives/C5UPMM0A0/p1701764501146389>

Not an arrow fan. I build my web layer to only throw from a custom set of exceptions that my global exception handler can map to appropriate responses