This repository has been archived by the owner on Oct 23, 2023. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 135
Add Stacktrace Option to CaptureMessage #332
Comments
I think this makes sense, but not going to be a high priority issue right away. Thanks @BigPrimeNumbers |
@BigPrimeNumbers done #388 |
Very nice to see implemented, though it looks to only be supported via a global flag being set (so all calls to raven-js version of captureMessage: function(msg, options) {
...
if (this._globalOptions.stacktrace || (options && options.stacktrace)) {
options = objectMerge(
{
// fingerprint on msg, not stack trace (legacy behavior, could be
// revisited)
fingerprint: msg,
// since we know this is a synthetic trace, the top N-most frames
// MUST be from Raven.js, so mark them as in_app later by setting
// trimHeadFrames
trimHeadFrames: (options.trimHeadFrames || 0) + 1
},
options
);
... |
This is easily doable and actually will help us unify both codebases. Reopened. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It'd be great to have the option with the method
captureMessage
to enable a stack trace,similar to raven-js. As of right now, it appears that
captureException
is the only way to get a stack trace.The text was updated successfully, but these errors were encountered: