Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Question: Can you explain why you swallow exceptions in SerilogExceptionContext and SerilogRequestMessage #1

Open
OutOfTouch opened this issue Aug 18, 2015 · 0 comments
Open

Question: Can you explain why you swallow exceptions in SerilogExceptionContext and SerilogRequestMessage #1

OutOfTouch opened this issue Aug 18, 2015 · 0 comments

Comments

@OutOfTouch
Copy link

Hi,

I know this is an example and I am glad you shared, I got here from a StackOverflow question you answered, I am wondering why you swallowed any exceptions that might occur in SerilogExceptionContext and SerilogRequestMessage? Is this so we don't lose our unhandled exception to exception handling code?

Thanks!
@OutOfTouch OutOfTouch changed the title Question: Can you explainwhy you swallow exceptions in SerilogExceptionContext and SerilogRequestMessage Question: Can you explain why you swallow exceptions in SerilogExceptionContext and SerilogRequestMessage Aug 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@OutOfTouch