Put rounding-related resolvedOptions properties in alphabetical order

[ben-allen]

Description

This is a very small change -- it just puts the rounding-related properties of the object returned by Intl.NumberFormat.resolvedOptions() and Intl.PluralRules.resolvedOptions() in alphabetical order.

Motivation

This makes the text marginally more readable, and has the advantage of reflecting the output order as currently defined in the spec.

Additional details

See tc39/ecma402#811

[github-actions]

Preview URLs

• /en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat/resolvedOptions
• /en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/PluralRules/resolvedOptions

[Josh-Cena]

We do align with the spec on property order. I was about to say that but I realized the spec changed too! Thanks!

[ben-allen]

@Josh-Cena The order of properties in the objects returned by resolvedOptions for many of the Intl objects doesn't match the spec order. See, for example, the spec for Intl.ListFormat.prototype.resolvedOptions(), which has "type" before "style" in the associated table, whereas the MDN page has style before type.

Would it be worthwhile to go through and put these properties in spec order across MDN's Intl documentation, aside from properties where putting them in spec order would be confusing (i,e. ones where there's special rules, as with the properties in NumberFormat related to number of fractional digits and number of significant digits?

I'm particularly noticing (and particularly want to change) resolvedOptions() documentation where locale isn't the first property listed, for example on the page for Intl.NumberFormat.prototype.resolvedOptions().

[Josh-Cena]

So, I thought I already did that long ago, but I just went to check and saw that it's still stashed in my local repo.

Could you wait a few weeks? I'll try to finish my existing work on unifying resolvedOptions format. If I couldn't get it done then, you could go ahead.