is there something like isort for js?

[surchs]

I notice we sometimes have diffs to re-sort object keys and such things. Is there maybe some tool we can configure to go through the whole codebase once to make the appropriate changes, and to then keep on top of this - e.g. as part of a pre-commit check?

[jarmoza]

@surchs I believe we can do this by adding the "sort-keys" rule to the eslint rc file, and then by installing/configuring this plugin.

[surchs]

Cool! I'm in favour of adopting the eslint rule to keep things consistent. I'm less clear about the tool, it looks not very widely adopted / maintained. I could imagine that having the rule enabled and configured to show up in the IDE (and during pre-commit) might be sufficient here. wdyt?

[jarmoza]

'sort-keys' definitely works. I tried it out before I commented earlier. I can see it being annoying to the coder to do it manually. I'm alright with it though myself.

That said, I don't know if eslint --fix will alphabetize it. If so, then that's even better.

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days.
We have applied the stale-issue label to indicate that this issue should be reviewed again and then either prioritized or closed.

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days.
We have applied the stale-issue label to indicate that this issue should be reviewed again and then either prioritized or closed.

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!