Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion how should we handle long inspects in failure messages?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Alex Chaffee  
View profile  
 More options Dec 5 2010, 10:59 pm
From: Alex Chaffee <a...@stinky.com>
Date: Sun, 5 Dec 2010 19:59:34 -0800
Local: Sun, Dec 5 2010 10:59 pm
Subject: Re: how should we handle long inspects in failure messages?

On Sun, Dec 5, 2010 at 6:31 PM, Steve Conover <scono...@gmail.com> wrote:
> So wait, what happens to the inspect that's 3 pages long (because Rack
> Request points to a bunch of objects internally that you don't care
> about)?

It's still 3 pages long but it's indented.

I'm not saying it's perfect, and maybe we'll want an option to truncate
instead of or in addition to the indentation, but please try it out and see
if you can stand it. Remember, someone might actually care about that deeply
nested object someday.

I'm working on a Rack app right now so I'll get a chance soon to see what a
real Rack request looks like.

 - A

--
Alex Chaffee - a...@stinky.com - http://alexch.github.com
Stalk me: http://friendfeed.com/alexch | http://twitter.com/alexch |
http://alexch.tumblr.com


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.