spire-io/shred — Issue #23: Attach original request to shred error
Author: thedaniel
Created: 2012-02-25 01:30:51+00:00
State: open

This way, if an error bubbles up from within some nested Shred requests, we can easily tell which request caused the error.

current:

```
{ message: 'ResponseError: 406',
response:
406
- Headers:
,
status: 406 }
```

proposed:

```
{ message: 'ResponseError: 406',
response:
406
- Headers:
,
status: 406,
request:
}
```