Before, this API was not returning the width and height properties (at least, it wasn’t returning those with our way of building our query). This seems to be something new, which in turn broke our products because it overrode our own width and height properties (we were looping on all of the Attachment record properties to dynamically copy those properties into an aggregated record which contains a mix of the Attachment record and the Asset record).
This kind of small changes should be documented, there is no changelog whatsoever, nor any kind of versioning. This is something that has always bothered us, as any change made to the API will be applied to all customers at once and there is no way to even know what’s gonna change. I don’t even now since when this issue occurs, it’s not really reassuring.
Also, note that I like the change, the original width/height properties were definitely missing there and it was complicated/unreliable to figure them out (had to dig into the thumbnails property). So, it’s a good change.
It simply lacks good communication/transparency, and probably a way to enable such new feature, maybe by providing a HTTP header as a flag, to avoid breaking existing apps.