style: indent lines with tabs instead of spaces

[Belco90]

Checks

• I have read the contributing guidelines.
• If some rule is added/updated/removed, I've regenerated the rules list (npm run generate:rules-list)
• If some rule meta info is changed, I've regenerated the plugin shared configs (npm run generate:configs)

Changes

• Configure prettier to indent lines with tabs rather than spaces
• Set up lint-staged using a js config file, so ignored files can be excluded properly

Context

There was no ticket for this. However, Prettier is considering switching to tabs by default in v3. This is a great change, you can find the motivation behind it here: prettier/prettier#7475

I think we should switch to tabs now to improve the accessibility of the code. The tab size can be customized in GitHub here: https://github.com/settings/appearance

[MichaelDeBoey]

LGTM!

Not sure if we already need to do it before the Prettier discussion is resolved though. 🤔
I would personally wait for it & do it together with the Prettier v3 update.

[Belco90]

Not sure if we already need to do it before the Prettier discussion is resolved though. 🤔
I would personally wait for it & do it together with the Prettier v3 update.

Not sure what Prettier discussion you are referring to, but the original issue for v3 is still open.

Since the first alpha for Prettier v3 was released a few days ago with no change related to using tabs, I'd just switch to tabs in our codebase. If they do the change in v3, we are ready for it. If not, we made our codebase more accessible, even if Prettier didn't change its defaults!

[MichaelDeBoey]

@Belco90 I was indeed referring to the original issue that's still open.

If not, we made our codebase more accessible

I think that's the whole discussion, that it's not 100% sure it's more accessible.
If it was 100% sure, Prettier would switch in a second.
Since it's not, that's why the discussion is still open.

I think we should have waited to see what the outcome of the discussion is, especially since the only reason we're doing this change is because of something that's not 100% resolved/clear.

[github-actions]

🎉 This PR is included in version 5.6.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀