4 ms·

Depends on who you're targeting (developers know how to make sense of types etc) and how well you translate the error info to human-readable error messages. Mo

• dspillett 13y ago
  > Depends on who you're targeting (developers By all means have a developers mode which does hand out the information more readily (though I tend to be wary of that in case it gets left on in production, and because it is an extra code path that needs to be properly tested), or report the detail directly if it is an internal tool. But the post I was referring to infored (to my mind) handing the detail out to end users (and by "end users" I mean the untrustworthy mob that is the general public). > It's also not necessary to present all the information to your users, you can also make better error logs that users can send to the developers. Hence my last para, where I suggest giving the user reference to the detail without giving them the actual details (the code to give to you for looking up the stored exception report). Giving all the info to the user as an encrypted package would work too (in that case "please quote this code in any issue reports" becomes "please copy+paste this block of text into any problem report").
• einhverfr 13y ago
  One option is to log everything but display something simple to the user.