feat: Extract correct type and value from top-most error

[kamilogorek]

Fixes #70 cc @mfridman @fedoricobond

[matianjun1]

@kamilogorek For v0.6.1 how about this feature?

[kamilogorek]

I'm not sure what is the question here. We already shipped this change a long time ago.

[matianjun1]

I'm not sure what is the question here. We already shipped this change a long time ago.

@kamilogorek Sorry for my description. For the newest release. This feature has been remvoed. Both of the test code.

sentry-go/client_test.go

Lines 125 to 143 in af3076c

	errorChainTests := []captureExceptionTest{
	{
	name: "MostRecentErrorHasStack",
	err: pkgErrors.WithStack(&customErr{}),
	want: []Exception{
	{
	Type: "*sentry.customErr",
	Value: "wat",
	// No Stacktrace, because we can't tell where the error came
	// from and because we have a stack trace in the most recent
	// error in the chain.
	},
	{
	Type: "*errors.withStack",
	Value: "wat",
	Stacktrace: &Stacktrace{Frames: []Frame{}},
	},
	},
	},

This should be *sentry.customErr not "*errors.withStack

[rhcarvalho]

@matianjun1 in v0.6.0 we added full support for chained errors, see #185.

Now we report a complete chain of errors, as supported in other platforms and described here: https://develop.sentry.dev/sdk/event-payloads/exception/.

If you found a bug or have a feature request, please open a new issue.