allow to trigger an error manually (with custom data for debugging)
this way I could send an error under special circumstances and include custom data, like a stack trace. This would also help to work around the issue mentioned here: http://errorception.uservoice.com/forums/132896-suggestions-and-feedback/suggestions/2387893-send-a-stack-trace-with-the-error
Karl Baum commented
Custom data is definitely needed as often times i do not see the errors reported. I have a feeling that if i knew the username, i could log in as that user and see the same error.
Christopher Froehlich commented
This would be useful. My library handles nearly all exceptions internally, and I have the call stack as well as various useful data points like the current user, location, action, etc. So errorception is only catching the errors I haven't trapped.