ResponseAs<R>() api method
it doesn't work yet as it hasn't been tested
But it should work for responses in either json or xml (assuming that json responses have a valid content type)
Simplest success case tests on ResponseDeserializer
tests on ResponseDeserializer
And a refactor.
I want this class to take over from StringDeserializer, but not yet. Added JsonParseFailedException for general case of response not being parsable as json. It seems that if the property names don't match up then the json parser lets it slide, so there's no exact analogy to UnexpectedXmlContentException
integration test on ResponseAs()
Will check later if this works.
Fix failing integration test
Merge branch 'master' into ResponseAs
Moved ResponseDeserializer into the "Parsing" folder
as it seems to belong better there
Moved responseAs test to different file
as it's not the same thing as the StatusTests - it's using the status endpoint as a simple e.g. of a working endpoint,
not testing that it is working
All extension methods should be in the root namespace
i.e. in namespace SevenDigital.Api.Wrapper not  SevenDigital.Api.Wrapper.Extensions
despite the folder structure
So that they can be found easily by consumers without adding another "using" statement
This was mostly true, just not consistent
Merge pull request #168 from AnthonySteele/ResponseAs

Response as
Merge pull request #170 from AnthonySteele/extension-namespace-tweaks

All extension methods should be in the root namespace