Added settings keys sorting

[cub-uanic]

I'm using Git to store my progress in dotfiles and share them between several hosts.
Sometimes, on different hosts, I'm getting the keys in json in a different order.
This makes it difficult to understand exactly what was changed (while in reality, it could be just one line), and also makes diffs larger.
As a solution, I suggest always sort the keys of the settings object.

(the idea is the same as I proposed in philc/vimium#4764)

[seanprashad]

Hi @cub-uanic! To sync progress across multiple hosts, you can sign in with your GitHub account:

Does this fit your use case? This was meant to replace the export/import functionality

[cub-uanic]

Hi @seanprashad,
Yes, I know about possibility to sign in via GitHub.
However, I'm old-fashioned :) and would like to store and manage my progress locally.

[seanprashad]

Change makes sense - just one small adjustment to ensure exports won't be malformed

[seanprashad]

Thank you very much!

[cub-uanic]

Seems we're lost the key point - sorting the entire payload, not just some of its keys:

const payload = {
    completed: [...completed].sort((a, b) => a - b),
    starred: [...starred].sort((a, b) => a - b),
    notes, solvedDates, reminders
}.sort();

I'm about the last line (untested)

[seanprashad]

Seems we're lost the key point - sorting the entire payload, not just some of its keys:

const payload = {
    completed: [...completed].sort((a, b) => a - b),
    starred: [...starred].sort((a, b) => a - b),
    notes, solvedDates, reminders
}.sort();

I'm about the last line (untested)

Did you see #533 (comment)? There's also instructions to run the website locally: https://github.com/seanprashad/leetcode-patterns#contributing

[cub-uanic]

Was in rush and missed it 🫡