I just love when an API returns a set of results, some have property X as a string and some as a JSON array. Wtf? Good people had put great API wrappers and it works if X is string as per service specification, but breaks otherwise, unsurprisingly.

I had to do a pull request to the wrapper repository to account for this inconsistency 😶

  • 1
    This was most certainly the great idea of a JS dev, because in the JS world, this bullshit is completely normal. It’s considered to be the strength of JS. I have seen this in popular frameworks.
  • 1
    @Lensflare I, a strongly typed guy, strongly condemn this
  • 1
    @olezhka everyone should
Add Comment