Romain

No problem, let me know how it goes!

Sorry you're right the work hasn't been fully ported. There is now support for multiple rendering engines, so we just need to include @mefernandez's great work into [lib/renderers/markdown/index.js](https://github.com/rprieto/supersamples/blob/master/lib/renderers/markdown/index.js).

Hi, where do you want the decoded URL to appear? The problem with decoding is you can end up with invalid URLs, e.g. if the route is `/things/:name` and the...

I see what you mean, it's not as easy to read as `checkInDate=2015-12-07T09:29:18.130Z`. The `:` character is actually valid in URL paths and queries, I'm not sure why is gets...

Thanks, I wasn't aware of `type('form')`. Does this set a `content-type: application/x-www-form-urlencoded` header?

Hi, thanks for the detailed report. Definitely a weird bug! Could you use the JSON renderer and post the corresponding section here? Trying to figure out if it's a problem...

That's very odd.... I'll try to reproduce it locally.

Potentially, as `supersamples` only normally expects 1 call per test (otherwise it wouldn't know which one to extract). But your example in the original message didn't have nesting did it?

Hi @FredKSchott, glad to hear it's useful! That's a good idea, not sure how to implement it yet. What we currently do, that might solve your requirement, is the first...

Ah you're right, for now `describe` blocks are only used for grouping / navigation, and `it` blocks are used to store Markdown and examples. I'll have a think about how...