Skip to content

Conversation

@kamilogorek
Copy link
Contributor

Fixes #2211

We have this implemented correctly in CaptureConsole integration :<

if (level === 'assert') {
if (args[0] === false) {
message = `Assertion failed: ${safeJoin(args.slice(1), ' ') || 'console.assert'}`;
scope.setExtra('arguments', normalize(args.slice(1), 3));
hub.captureMessage(message);
}
} else {
hub.captureMessage(message);
}

@kamilogorek kamilogorek requested a review from HazAT September 12, 2019 10:57
@getsentry-bot
Copy link
Contributor

Warnings
⚠️ Please add a changelog entry for your changes.
Messages
📖 ✅ TSLint passed
📖

@sentry/browser bundle gzip'ed minified size: (ES5: 16.207 kB) (ES6: 15.3867 kB)

Generated by 🚫 dangerJS against a522e7f

@HazAT
Copy link
Member

HazAT commented Sep 17, 2019

+Changelog

@kamilogorek kamilogorek merged commit 5907ce6 into master Sep 20, 2019
@kamilogorek kamilogorek deleted the assert-fail-only branch September 20, 2019 10:23
mydea added a commit that referenced this pull request Apr 26, 2024
I'm seeing a lot of breadcrumbs for `console.assert`s even though they
are passing. This issue was previously fixed in #2239 but I guess there
was a regression at some point. There was already an existing test case
for this, but it was missing an assertion.

---------

Co-authored-by: Francesco Novy <francesconovy@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

console.assert adds a breadcrumb even when assertion doesn't fail

3 participants