📐 formatting rules

[juli4nb4dillo]

Added https://eslint.style/packages/default stylistic plugin for formatting, and enabled a few rules:

• Consistent indent to 2 spaces
• Space infix operators
• Space on curly brackets for objects.

I want to enable always semicolon, in general is an excellent rule (some bugs are harder to spot due to lack of semicolons), I'll let you decide.

[alexrudd2]

I want to enable always semicolon, in general is an excellent rule (some bugs are harder to spot due to lack of semicolons), I'll let you decide.

Fine with me. I don't have strong preferences for TypeScript anyways. Well actually, I had been considering just switching to Biome. eslint and its plugins seem to break compatibility a lot

What's been keeping me from doing any type of formatting changes is a desire to keep in sync with upstream, but it's becoming more and more likely that it's just abandoned. I'll reach out again.

[juli4nb4dillo]

@alexrudd2 are there downstream changes we can adopt?

[alexrudd2]

@alexrudd2 are there downstream changes we can adopt?

There have generally been two contributors of interest.
@jedahan knows about this fork, and helped implement the brushless mode (note: it's not fully working). We've got contact via email.
@osresearch pops up every now and then with PR's to saxi upstream. (example: nornagon#213). I pay attention, but haven't established contact.

Here's the project where I tried to track upstreaming changes: https://github.com/users/alexrudd2/projects/1

[alexrudd2]

I've emailed @jedahan re: the state of saxi upstream. Let's see what he says.

[jedahan]

I am happy to adopt any automated tooling like formatters, and if i need to re-create/submit/fix features can do so now that I have my plotter back at home.

If we are okay with larger divergence in some longer-term future, I've started things like writing some typescript apis for interfacing with EBB commands

[jedahan]

I see this fork as the experimental cousin of upstream, so if we think formatting is good, its good to try here first, and then show upstream and hope they see the benefits too.

[alexrudd2]

I see this fork as the experimental cousin of upstream, so if we think formatting is good, its good to try here first, and then show upstream and hope they see the benefits too.

@jedahan As of now this is now the main development repository. I released 0.16.0 last night, so let's go for the other changes now :)