3.0.1: NumberWang
Argo 3.0 changed the way Booleans were decoded and in doing so, accidentally broke JSON parsing for APIs that didn't quite follow the JSON spec. Specifically, @jshier noted that it's moderately common for APIs to return 1
or 0
instead of true
or false
..
To address this, we've re-added the capability of Argo to recognize Bool
values represented in the JSON as numbers.