captureMessage does not send context's additional data

[ironsidevsquincy]

Couldn't find an issue relating to this, so...

When using context to wrap a function call, with additional data, e.g.

Raven.context(
    { tags: { foo: 'bar' } },
    myFunc
);

if Raven.captureMessage is called from within myFunc, the tag foo is not sent up to sentry

Looks like it only sends the global options - https://github.com/getsentry/raven-js/blob/master/src/raven.js#L659

Is this expected behaviour?

[benvinegar]

It is expected, albeit perhaps not straightforward.

context basically produces a function that does this:

try {
  myFunc.apply(this, arguments);
} catch (e) {
  Raven.captureException(e, { tags: { foo: 'bar' } });
}

If inside myFunc, Raven.captureException is called (but doesn't throw an exception), it has no knowledge of the tags you've set higher in the stack via context. context is just an alternate form of wrap, and poorly named; it doesn't "set a context" that is interpreted further below.