Open azu opened 4 years ago
Currently, I use both eslint-plugin-typescript-compat
and eslint-plugin-compat
in my project.
It works.
We have a option is that restricts eslint-plugin-typescript-compat
's role to only method.
It causes a naming issue.
eslint-plugin-typescript-compat has same feature to eslint-plugin-es and eslint-plugin-compat. But This rule takes a different approach.
eslint-plugin-typescript-compat can lint prototype method using TypeScript that is different point for other rules. However, Class, static method detection will be the same as eslint-plugin-compat.
I do not want to create duplicated rules.