Skip to content

fix: Use fallback stacktrace for events which have no stacktrace #131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 21, 2019

Conversation

kattrali
Copy link
Contributor

Capture and use a stacktrace from the notify() handle if an event is
reported without a stacktrace (such as logging a string or other non-
Exception object).

Tests

Manually verified the behavior by logging messages, i.e. Debug.LogError("foo")

Review

For the pull request reviewer(s), this changeset has been reviewed for:

  • Consistency between the changeset and the goal stated above
  • Internal consistency with the rest of the library - is there any overlap between existing interfaces and any which have been added?
  • Idiomatic use of the language

Copy link
Contributor

@snmaynard snmaynard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SGTM

Capture and use a stacktrace from the notify() handle if an event is
reported without a stacktrace (such as logging a string or other non-
Exception object).
@kattrali kattrali force-pushed the kattrali/use-fallback-stacktrace branch from 441e109 to 6422e73 Compare February 21, 2019 15:43
@kattrali kattrali merged commit d572578 into master Feb 21, 2019
@kattrali kattrali deleted the kattrali/use-fallback-stacktrace branch February 21, 2019 16:43
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