Huh, I have a different impression. Take this doc, that I was staring at the other day: https://docs.microsoft.com/en-us/rest/api/containerregistry/manifests/ge

Huh, I have a different impression. Take this doc, that I was staring at the other day: https://docs.microsoft.com/en-us/rest/api/containerregistry/manifests/get-list https://docs.microsoft.com/en-us/rest/api/containerregistry/... ; it is for listing manifests in an ACR repo. The "orderby" query parameter is documented as "orderby query parameter". It is secretly an enum; the values are things like "time_asc" and "time_desc". Later, take the response. "lastUpdateTime" is documented as "Last update time". It's documented as a string, which while technically correct (at the JSON level, yes, it is a string, ish), is wrong. It's an RFC 3339 datetime — I think¹ — but it's also wrong because it is — bizarrely — optional. I actually don't know what sets it, and I have no examples of it being set and the docs don't help. I could also refer one to their documentation about the various performance characteristics of various Azure VM types. Some VM types just aren't listed, so if you're curious about those, good luck, I guess? Run them yourself? We've also hit things like various tri-bools. IIRC, whether you're on a paid SKU for AKS is a weird tribool of sorts. The field has two values, represented by three values: "Free" (meaning free), "Paid" (meaning paid) and the field simply not being present at all, meaning the same as "Free". Not only is the chosen representation terrible, that it is this way is undocumented. ¹I don't have a counter example yet, at least…