Make exceptions useful from the command line #79
Conversation
I frequently use curl testing in Rails, but when better_errors intercepts an exception on those requests I get a large output that is unusable at the command line. I simply added an HTML comment to the end of the HTML that includes the exception and backtrace. This shouldn't effect viewing the page in the browser at all, but makes life at the command line much easier when tracking down errors. Example output, trimmed for brevity: https://gist.github.com/4347455
|
Wouldn't a better solution be to check if the user agent is curl or wget and only display that exception and backtrace? |
|
@sebmck perhaps, but it seems like switching on the user agent would add unnecessary complexity. Whereas, always including it in the footer of the html is benign when using a browser. Very helpful on the command line. And we don't have to maintain a list of command line clients that want text only output. For example, I just started using the awesome httpie client and we would have to update the user agent check to include it. |
|
this seems simple enough to be harmless for now, and it can always be improved later on (user-agent detection and whatnot). thanks for the contribution! |
Make exceptions useful from the command line
|
I've extended this to check for the HTTP Tested that it works for curl, wget, Chrome, and Firefox. |
|
Oh, and might I add it makes Markdown-formatted error messages, like this. Perfect for pasting into Trello or Gists. |
I frequently use curl when testing my apps, but when better_errors intercepts an exception on those requests I get a large output that is unusable at the command line. I simply added an HTML comment to the end of the HTML that includes the exception and backtrace.
This shouldn't effect viewing the page in the browser at all, but makes life at the command line much easier when tracking down errors.
Example output, trimmed for brevity: https://gist.github.com/4347455