Support top level array responses

[raul]

While adding support for top-level array responses I found JSONResponseVerification's internals a bit complicated so I refactored them. Some notes:

• I've replaced #validate_hash_response with a more vague #verify: the input now can be a hash or an array, and once we extend WD so specify response headers and status code we'll probably want to verify headers, status code and the response body under a single #verify public method. The old method is still supported as an alias, but I'd like to remove it once we bump to a new version if this PR gets approved.
• To avoid passing errors around, they are now returned in nested arrays which get flattened before being returned.
• This is the first time I apply Yard to document methods, so I'd appreciate a quick review in the doc comments.
• I've respected the original way of managing an unknown data type (printing a message and not verifying it at all), though it may be better to raise an exception instead.

All specs are passing but I don't have an actual production API to test it yet, so cases not covered by the test suite may break.

[mattetti]

Sorry I totally missed this PR. It looks good to me, the change of method name might break a few things tho, but that's also easily fixable and the new name is actually better.

[raul]

Thanks @mattetti – are you willing to keep WS active or are you more focused on Go-based APIs these days? :) Since I read your post I'm really tempted to learn Go and use it instead of Ruby for any small API that I need to work on.

[mattetti]

I'm willing to keep WS active but would def. need some help maintaining the project. For my own startup i'm using Rails for the frontend and Go for the API so I'm using WS for this specific project.

[kamui]

Since reading some of your tweets and Go articles I've also been considering trying out Go to build an API. Planning any posts about your experiences building your API in Go?

[mattetti]

I'm planning on writing a book but that won't happen until my startup is launched :)

On Tue, Aug 20, 2013 at 4:44 PM, Jack Chu notifications@github.com wrote:

Since reading some of your tweets and Go articles I've also been considering trying out Go to build an API. Planning any posts about your experiences building your API in Go?

— Reply to this email directly or view it on GitHubhttps://github.com/mattetti/Weasel-Diesel/pull/25#issuecomment-22986259 .

[raul]

Can you please sign me up as a beta reader? :)