Something that happens to me a lot while web programming: I want to run an operation that has a chance of failure. On a failure, I want to send the client a 500. Normally though, I just want to continue executing a series of steps.
doSomeWebStuff :: SomeWebMonad ()
doSomeWebStuff = do
res <- databaseCall
case res of
Left err -> status 500
Right val -> do
res2 <- anotherDatabaseCall (someprop val)
case res2 of
Left err -> status 500
Right val2 -> text $ show val2
since the errs are exceptions, I don’t like that I need all that case stuff just to catch them. I want to do the same thing whenever anything is a left. Is there a way to express that on one line with something like guard, but control what it returns on an exit?
In another language I could do this:
function doSomeWebStuff() {
var res = databaseCall()
if (res == Error) return status 500
var res2 = anotherDatabaseCall(res.someprop)
if (res2 == Error) return status 500
return text(res2)
}
So, I’m ok writing some boilerplate, but I don’t want the errors to mess with my nesting, when it’s far more common to just want to continue forward with the found case.
What’s the cleanest way to do this? I know in theory I can use a monad to exit early on a failure, but I’ve only seen examples with Maybe and it would return Nothing at the end, rather than letting me specify what it returns.
Here’s how I would do it with
ErrorT. Disclaimer: I have never actually usedErrorTbefore.Here are the imports and type declarations I used to make sure it all typechecks correctly:
If I’m doing this all wrong then please, somebody shout out. It may be wise, if you take this approach, to modify the type signature of
databaseCallandanotherDatabaseCallto also useErrorT, that waya <- ErrorT bcan be reduced toa <- bindoSomeWebStuff'.Since I’m a complete noob at
ErrorT, I can’t really do any hand-holding besides “here’s some code, go have some fun”.