adding setContextsInterface

[orlando]

Context

This PR adds setContextsInterface method, which allows using the Contexts Interface.

A use case is when using this library in React Native. You can send device and os information along with the error.

Notes

• The user has to know about how the Contexts Interface works. Given that not every key is valid.
• We don't send this data unless the user uses the method (or access the _globalContext private variable directly)

Media

Before

After

[dcramer]

@getsentry/javascript we should talk in person, but I'm +1 on getting an API in for this, but likely under a more friendly interface.

I put 10 seconds of thought into this, but e.g.

Raven.setContext('foo', {})

• We'd probably also want to call it set vs add since it'd overwrite that keyname
• We probably don't need interface in the function call

[orlando]

Great @dcramer,

I like that interface. One thing to keep in mind is how we handle calling this method with no arguments or with the second argument missing.

But let me know what changes we should do to get this merge.

Thanks!

[orlando]

hey @dcramer any update on this?

[dcramer]

@getsentry/js

[dcramer]

Welp maybe @getsentry/javascript

[benvinegar]

@orlando – a couple things:

1. There is a new React Native plugin in the works that will provide this information automatically.
2. I find the naming of "contexts" interface confusing. There are already setUserContext, setExtraContext and setTagsContext, not to mention getContext and clearContext. I am not fond of bloating the API further with setContextsInterface, which further strains the meaning of "context" and adds a new term, "interface", which has not been exposed in the naming scheme before.

Option 2 makes me want to just punt until the new RN client is out.

[orlando]

@benvinegar great!. Thanks for the info. Can't wait to kill my fork.

Thanks again!