minor: Include the error/exception capture in the new example flow #126
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
After pulling master in #120, I noticed that the structure of
examples/main.gohas changed.This follow-up PR updates the
error trackingexamples to match the new format, keeping them consistent.This PR introduces no changes to core functionality; only example updates.
Proof of work:
Updated Menu:
Option 6
Error tracking with enqueue examples:Option 7
Error tracking with log handler examples:The exception capture also shows up in the "All" run:
Exceptions are correctly captured in the UI:
