At present we're depending on an EXTREMELY old version of clj-stacktrace which totally does most of what we want - but it doesn't render ex-data when showing causes and stack frames. Which is a serious limitation since Katamari's entire exception / tracing story is driven by trying to recursively capture context and inputs in chained ex-info instances.
At present we're depending on an EXTREMELY old version of clj-stacktrace which totally does most of what we want - but it doesn't render
ex-data
when showing causes and stack frames. Which is a serious limitation since Katamari's entire exception / tracing story is driven by trying to recursively capture context and inputs in chainedex-info
instances.