Feat: Adds an option to disable capturing Debug.LogError as events #2009
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bitsandfoxes
approved these changes
Feb 10, 2025
Contributor
bitsandfoxes
left a comment
bitsandfoxes
left a comment
There was a problem hiding this comment.
Thanks for the contribution! 🔥
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the SDK captures any logs sent with
Debug.LogErroras an event. There are some ways to mitigate this, such as by using aBeforeSendcallback, but the filtering risks over (or under) filtration, and isn't completely clear on how to accomplish this.Since there are already options to enable/disable breadcrumb capturing, I've added one to enable/disable the functionality for events too.