"Wouldn’t it be great if you could see errors in place instead of mysterious NULLs?"
It's not a good ad when the error message is inadequate even in the supplied example and you need to hack around it.
It's not a good ad when the error message is inadequate even in the supplied example and you need to hack around it.
error({
stage: "transform",
err: "input error",
value: {
stage: "normalize",
err: "input error",
value: {
stage: "metrics",
err: "divide by zero",
value: {
sum: 123.5,
n: 0
}
}
}
})
There's no need to repeat the infamous MSSQL "String or binary data would be truncated" message saga here - there's no reason you can't give much more verbose errors by default.