Since fields are returned as nested JSON this is in line with how the JSON spec works.

BUT... the YAML serialization does care about order. So if Airtable's API randomly returns fields in a different order it will produce different YAML, which means if it's being kept in a git repo you'll get a pointless commit - e.g. this one: natbat/rockybeaches@96acfae