Wrong parameter name in Mturk error messages about aws-elixir

[4knahs]

Sorry for the late reply. From what i recall i tested just mturk, haven't touched that code in a long time though.

[jadeallenx]

Thanks for the message. This code is autogenerated by aws-codegen, so it is likely an error in the template which assembled this module for this API.

That's more than I have time to manage today but I will look into it.

[4knahs]

I correct my previous statement, the error messages aren't always nil.

Apparently the first letter case is arbitrary across requests.. Here is a response body to AWS.MechanicalTurk.list_h_i_ts\3 with lower case:

%HTTPoison.Response{
    body:
      "{\"__type\":\"ValidationException\",\"message\":\"1 validation error detected: Value '1000' at 'maxResults' failed to satisfy constraint: Member must have value less than or equal to 100\"}",
    headers: [
      {"x-amzn-RequestId", "4481aec4-ac71-4517-bbb8-3d3125440041"},
      {"Content-Type", "application/x-amz-json-1.1"},
      {"Content-Length", "181"},
      {"Date", "Mon, 09 Apr 2018 10:22:03 GMT"},
      {"nnCoection", "close"}
    ],
    status_code: 400
  }

[jfacorro]

@4knahs Do you know if this applies only to the mturk integration or to all of them?

[jfacorro]

After some investigation the shape of the error depends on the API being used and the specific error returned. A possible approach is the one described here which involved returning the full (decoded) error.

[jfacorro]

The clients are returning the whole parsed error in latest master now to avoid having to figure out the different paths to the message and code.