✨ Sort key codes in keybinds export

[injust]

Feature Request Description

If you have a keybind with multiple arrow keys (e.g. ← ↑ for the top-left quadrant), the UI always displays the left arrow first.

However, the ordering of the key codes in the exported JSON seems to be based on the order you press the keys when setting the keybind. So if you rebind a keybind but press the arrow keys in a different order, the key codes will be reordered.

It seems like the ordering of the key codes doesn't affect how the keybind is actually used. If this is actually the case, it'd be a nice-to-have to sort the key codes so the exported values stay consistent.

Screenshots

No response

Additional Context

No response

Final Checks

• My issue is written in English
• My issue title is descriptive
• This is a single feature request (multiple feature requests should be reported individually)
• I can help with the improvement or development of this feature (tick if you can help)

[SenpaiHunters]

Wow, it's been a bit since I've seen this. Can you now update and take a look at it? The whole exporting process has been changed a few times. It may order it better now, but if it doesn't, I can add some logic to make the ordering and sorting a bit more aesthetically pleasing when exporting. Although, it's more of a quality of life improvement when viewing, rather than an essential feature.

[injust]

I'm using version 1.3.0 and it doesn't seem to be any better. The JSON layout seems to be randomized every export, even if you don't change any of the settings.

[injust]

@SenpaiHunters I just noticed that #708 sorts the JSON keys (which is awesome), but the key code arrays are still unsorted.

e.g. this is what a diff of my Loop keybinds export looks like (after running through Prettier):

And the order is randomized on each export.

[injust]

@SenpaiHunters Gentle ping, could you please reopen this issue?

[SenpaiHunters]

Hey, it's recommended you make a new issue, rather than open a new issue. However, as it's apart of this, a 2 part fix, i'll add it into Loop in a later commit. It shouldn't be too much of an issue, but it won't be for a bit as it's really only visual and does not affect Loops internal logic.