Docs: Prioritize formatting rules over other, less-important ones in docs about typescript-eslint HOT 8 CLOSED

Yep, nice to see how plan adopted user needs, even if it didn't align with devs plans for next major release.
Huge kudos to them for prioritizing our experience even if it would require more work/support from them. 🙇

I see how this approach to rules might be actually helpful with new TS proposal microsoft/TypeScript#58019
I would like to force in which order I would want to force props/union order.

from typescript-eslint.

Very excited to see this land! I have one concern though. I'd like to propose a rule that bans any ASCII characters in variable names, due to to their potential for confusion, with an option to require only emoji as identifiers. I think this would a huge win for accessibility in a codebase, since emoji are language-independent. Would that fall under formatting or would we have an additional category for accessibility?

from typescript-eslint.

@kirkwaiblinger that makes a lot of sense. I'd love to see experimentation on a Prettier plugin that auto-replaces variable names with emoji equivalents. I imagine migration pain from the few projects still using ASCII characters in variable names might be severe for the few projects still on that outdated practice.

@IllusionMH indeed. That proposal does seem to blur the line between the linter and the compiler: a line that we haven't seen blurred much before. It'll be interesting to see them iterate on this new area over the next decade.

from typescript-eslint.

@kirkwaiblinger that makes a lot of sense. I'd love to see experimentation on a Prettier plugin that auto-replaces variable names with emoji equivalents. I imagine migration pain from the few projects still using ASCII characters in variable names might be severe for the few projects still on that outdated practice.

I’m honestly shocked that you have not enabled this in all of your repos yet https://www.dont.ninja/rules/prefer-emoji

from typescript-eslint.

Ah! I did not know that project exists, but it's good to see. Thanks @rubiesonthesky.

It looks like we can close this issue out as wontfix. Given that another project does things better than we ever could I don't see a need to keep investing in this area of typescript-eslint. Cheers all!

This was an April Fool's Day 2024 post. Happy don't-take-anything-on-the-internet-seriously day!

from typescript-eslint.

Heh, oops, thanks.

from typescript-eslint.

Could ts-eslint adopt these rules https://www.dont.ninja/ ?

Also I think ts-eslint would benefit this approach for formatting https://github.com/rohitdhas/shittier

from typescript-eslint.

This is still pinned 🦌

from typescript-eslint.