schema.cast reverses order of keys in objects

Describe the bug Keys are being reversed when casting an object.

To Reproduce https://repl.it/@rheidari/yup-reversing-keys

Expected behavior Expect the keys defined in the schema to be the same order coming out when cast.

Platform: Node v8.16.0

Additional context Noticed that there’s a .reverse() being called in sortFields. When I remove that it acts as expected, however I’m sure you had a reason for it being there https://github.com/jquense/yup/blob/1426feceb6c5544c526711bedcf388afaf6115b9/src/util/sortFields.js#L31

[TacianoBack]

You can try this in your validate function.

const shape = {
	name: yup.string().max(100),
	email: yup.string().max(60).email(),
}

const newShape = Object.entries(shape)
	.reverse()
	.reduce((prev, [key, value]) => ({ ...prev, [key]: value }), {})

const schema = yup.object().shape(newShape)

[rheidari]

Thanks for the explanation @jquense. Is there a way I can best go about re-ordering the cast object so that the original order of fields is maintained as per the schema, or will I need to do that outside of yup? I tried implementing a transform() on each object to recreate the object ordered by the Object.keys(schema.fields) but that didn’t seem to have any effect.

In my case I have a deeply nested object that will need to retain the order defined in each yup schema as I’m going to be transforming it back into XML.