Change callback parameter order about nano

[thiagoarrais]

If people choose to go with this, I am willing to do the changes, of course.

[dscape]

Hi Thiago,

This seems reasonable to me. And overall looks like a better api decision. The reason why it is the way it is is because of request. So I wonder what @mikeal thinks about this, maybe there's a reason he set the body as the last parameter of the callback?

If not I'll change this and set it as a 1.0 feature

[dscape]

This would also require:

• Updating the documentation
• Updating the blog post
• Updating all the tests

[thiagoarrais]

Sure. When I volunteered points 1 and 3 were certainly included (together with the library code, obviously). I am not sure I can mess with your blog, though...

[dscape]

@thiagoarrais messing with blog is fine :) Check dscape/dscape.github.com

If no one (@jchris, @pgte, @daleharvey) gives a reason why this would be a problem in the next 24 hours please do submit a pull request!

Thank you!

[mikeal]

is body a string or the parsed object?

why don't you parse the object and just set an _headers property on it?