Skip to content

Conversation

robinwassen
Copy link
Contributor

I added some additions to the docs in order to clarify that some of the optional settings only apply to the captureException call, and not the captureMessage.

Example of one more person than me that got confused by this: #196

If this is the expected behaviour is another discussion, but I think it is good if the docs make it clear how it currently works.

@mattrobenolt
Copy link
Contributor

Yeah, this is fair. The reason is because the url matching and stuff depend on fields that come from the Error object itself. They just don't apply to plain messages. :)

mattrobenolt added a commit that referenced this pull request Aug 11, 2014
Updated documentation with some clarification of the optional settings
@mattrobenolt mattrobenolt merged commit f12b40a into getsentry:master Aug 11, 2014
billyvg added a commit that referenced this pull request Feb 26, 2025
- fix(snapshot): Do not attempt to load iframe at all if it is blocked (#240)

See https://github.com/getsentry/rrweb/releases/tag/2.33.0
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.

2 participants