I had an issue where a lifecycle function returned a bool rather than a map, and it was rather opaque to debug where the issue was coming from. See the stack trace below:
I think we should catch and rethrow the exception in the lifecycle handling code, and dump the lifecycle and task name that caused the issue. It would also be good if we could name the anonymous function doing the merging based on the lifecycle name, however this would require a macro to wrap fn, to build anonymous named functions.
I had an issue where a lifecycle function returned a bool rather than a map, and it was rather opaque to debug where the issue was coming from. See the stack trace below:
I think we should catch and rethrow the exception in the lifecycle handling code, and dump the lifecycle and task name that caused the issue. It would also be good if we could name the anonymous function doing the merging based on the lifecycle name, however this would require a macro to wrap fn, to build anonymous named functions.