Add DefaultFormatter.EnableStacktrace

[gavv]

Add flag EnableStacktrace to DefaultFormatter that enables printing of stacktrace on failure. Formatted stacktrace should be added to FormatData (likely as slice of strings) and used in failure template.

See also #159.

[fahimbagar]

Hi @gavv, just checking.

What's the difference between this and the chain path? and what's the expected result here? 🤚

Sorry for the dumb question 😄

[gavv]

Hi, this issue is about regular go stacktrace / backtrace, like you see on panic or crash

https://dev.to/mcaci/reading-stack-traces-in-go-3ah5

It is possible to retrieve it programmatically from go runtime

[gavv]

Chain path, on the other hand, is a logical representation of path in httpexpect object tree

It doesn't include actual function frames, though it provides similar information in some sense

Most notably, chain path doesn't tell anything about location in user code. It shows path to object, but it doesn't show where that object were actually used when failure happened (maybe it was stored to variable and used later)

[fahimbagar]

Understood. I'll learn about go stacktrace / backtrace first and message you here afterward unless someone picks this up.
Thanks for the answer @gavv.

[diPhantxm]

Hi @gavv
I'm interested in this issue. May I take it?

[gavv]

@diPhantxm Sure, thanks!

[gavv]

Landed