I was going to add an explicit catch around executeSlow, but it turned out to be unnecessary because the code that actually calls AbstractStep.execute0() is smart enough to put the exception on the resulting Maybe. Here's the test showing that, and there's a test showing deep resolution of templates.
I was going to add an explicit catch around executeSlow, but it turned out to be unnecessary because the code that actually calls
AbstractStep.execute0()is smart enough to put the exception on the resultingMaybe. Here's the test showing that, and there's a test showing deep resolution of templates.