Describe the Bug

When using the schema export functionality, we noticed that on importing, all our fields on the list-o2m interface were reset to be alphabetically ordered. Upon investigating the schema.json file we saw that on a field under meta.options.fields the array has been sorted.

Fix in PR

To Reproduce

Added a relationship field with the list-o2m interface, add fields to the list in a non alphabetical order.
Run schema export, you might need to change something manually or in another environment for the hash to update, but once you then run schema import you'll notice those fields have now been sorted alphabetically.

Directus Version

10.9.0

Hosting Strategy

Self-Hosted (Docker Image)