My first reaction was to reject it because of renames like segs to segments, but I imagine that we could live with longer variable names or even add the most commonly used short versions to the skip list.

I also think that this would be positive. Is there something similar for markdown files so the docs are checked?

I also think that this would be positive. Is there something similar for markdown files so the docs are checked?

I'm not directly sure. Currently it may be possible to configure eslint to not only check js,ts etc.
But (if it is possible) we should do this in a further step/issue/pr.

For the plugin, I'd actually prefer one-time CLI tools or IDE extensions as I don't think spell check is something that important to persistent live in the CI process. We can run spell check once a while and fix them in a single commit so we don't need to sacrifice anything while keeping the commit history cleaner.

A nice thing using the lint step could be to show it directly in the review
I opened a discussion about that here: #2604

There is a VSCode Plugin: https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker
But it differs a bit and know some other worlds as the lint plugin

We could extract an additional lint script that specifically lint the project for spell-check. But in the end it is kinda the same as just running it in the normal lint step and otherwise folks would just forget to run it / the forget it.

For the plugin, I'd actually prefer one-time CLI tools or IDE extensions as I don't think spell check is something that important to persistent live in the CI process. We can run spell check once a while and fix them in a single commit so we don't need to sacrifice anything while keeping the commit history cleaner.

^ I agree with this - we could just run a typecheck tool once in a while. I don't really want spellcheckers to lint/affect source code variable names.

@Shinigami92 Maybe let's close this for now?