error handling is broken with 0.4.2

[proppy]

Given the following HTTP response:

400 Bad Request

{
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "INVALID_ARGUMENT",
    "message": "one of fields Query.query and Query.gql_query must be set",
    "debugInfo": "..."
   }
  ],
  "code": 400,
  "message": "one of fields Query.query and Query.gql_query must be set"
 }
}

0.4.2 calls the method callback with:

err: null
result: 'one of fields Query.query and Query.gql_query must be set'

While 0.2.13-alpha called it with:

err: { code: 400,
  message: 'one of fields Query.query and Query.gql_query must be set',
  data:
   [ { domain: 'global',
       reason: 'INVALID_ARGUMENT',
       message: 'one of fields Query.query and Query.gql_query must be set' } ] }
result: undefined

[rakyll]

Could you add a snippet for me to reproduce?

[proppy]

var googleapis = require('googleapis');
var datasetId = process.argv[2];
var compute = new googleapis.auth.Compute();
compute.authorize(function(err) {
    googleapis.discover('datastore', 'v1beta1')
        .withAuthClient(compute)
        .execute(function(err, client) {
            var datastore = client.datastore.datasets;
            datastore.runQuery({
                datasetId: datasetId
            }).execute(function(err, result) {
                console.log(err, result);
                console.assert(err, 'err should not be null');
                console.assert(!result, 'result should be undefined');
            });
    });
});

[rakyll]

requests was force trying to parse the responses to a JSON object with the prev version's options. #79 should be fixing your issue.

[proppy]

This indeed fixes the issue.