Fix: do not call captureException/captureMessage in a setImmediate

[glensc]

Somehow, doing so, will lose scope.setTag and scope.setExtra results

Instead, wrap whole setScope inside a function.

[glensc]

Perhaps should just not combine Sentry.withScope and setImmediate, but I moved everything, so it's simpler to understand.

[glensc]

@aandrewww please merge #34 or #32

I prefer #34 because it's a more compact change.

and release as 0.9.1 bugfix

[aandrewww]

@glensc hi.
I'm going to review, merge and bump version today or tomorrow.
Thanks!

[jdkajewski]

@glensc and @aandrewww, the only issue I foresee with this PR is that it does not set the proper log level. Where as with #32 it properly sets the log level.

[glensc]

@jdkajewski you just guess, or do you have a reproducer?

[glensc]

I just tested, code from this branch and info level gets logged as info to sentry as well

[gomerdoom]

@glensc The issue shows up with different log levels for exceptions. We're not seeing it capture the difference between fatal and error exceptions unless you call scope.setLevel, as well as pass the scope in as the second parameter on captureException.

[aandrewww]

I will review and test this PR tomorrow
Sorry for the delay :( (A lot of other stuff)

[glensc]

perhaps go with #32 then, or need to add scope.setLevel to this branch?

none of them matter much if v7 comes as there's a new API for transports

[aandrewww]

@glensc Hey. Sorry for long break.
I am going to merge #32 and bump minor version
Then I am going to review and merge #35 and bump major version

I think This PR should be closed

[glensc]

superseded by #32