[Feature]: Implement Rule to Ban Enums and Artificial Syntax in TypeScript

[dmytrokirpa]

Implement a rule to ban the use of enums and other artificial syntax structures in our codebase. This can be achieved through one of the following approaches:

1. Use Existing Tools:

   • Rule proposal: no-enum / ban-enum / no-use-enum typescript-eslint/typescript-eslint#561 (comment) or https://cartant.github.io/tslint-etc/ : these tools provide rules to ban enums, but we need to verify their current status and compatibility.

2. Port Existing Rules:

   • We can port the existing rules under the fluent project to our codebase.

3. Build Custom Rule:

   • We can develop a custom rule called no-artificial-syntax to ban enums and other artificial syntax structures by default, with an option to configure opt-outs for specific syntax structures.

Implementing this rule will help us maintain a cleaner and more manageable codebase. We welcome feedback and suggestions from the team on this proposal.

[bubulux]

Just out of curiosity: What is bad about enums? I often use them and would like to know why I should avoid them. Best Sam

[Hotell]

Just out of curiosity: What is bad about enums? I often use them and would like to know why I should avoid them. Best Sam

any kind of artificial syntax introduced by typescript is antipattern to use ( even TS team admitted that in retrospect, that's why TS will never introduce new artificial syntax and sticks to ECMA spec )

also check point 4 / https://medium.com/@martin_hotell/10-typescript-pro-tips-patterns-with-or-without-react-5799488d6680

[Hotell]

@dmytrokirpa we should rather move this issue to core repo and re-use it everywhere