As a developer, I do not want exceptions in logging to stop execution of my block/thread/app, so my code can continue to completion.
kana-ki opened this issue · 1 comments
kana-ki commented
Also, as a developer, I do not want exceptions in Libraries to hide an exception I'm attempting to log, so I can see my own more important exceptions.
Currently any exceptions thrown by NChronicle libraries are propagated up to the host application. This may cause problems such as NChronicle may hide a real exception with it's own exception whilst attempting to log it.
Solution:
Add an option to supress all NChronicle exceptions in calls to Chronicle.SendToLibraries
.
This option should be enabled by default.
kana-ki commented
We could add a logging exception handler, which the user can change.