azu / azu/eslint-plugin-typescript-compat
Merge to similar project?
- Dominant language
- TypeScript
- Stars
- 37
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
[eslint-plugin-typescript-compat](https://github.com/azu/eslint-plugin-typescript-compat) has same feature to [eslint-plugin-es](https://github.com/mysticatea/eslint-plugin-es) and [eslint-plugin-compat](https://github.com/amilajack/eslint-plugin-compat).
But This rule takes a different approach.
[eslint-plugin-typescript-compat](https://github.com/azu/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](https://github.com/amilajack/eslint-plugin-compat).
I do not want to create duplicated rules.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing eslint-plugin-typescript-compat with eslint-plugin-es and eslint-plugin-compat, focusing on prototype, class, and static method detection described in the issue. A completed outcome would be a maintainer decision about whether to merge with a similar project or keep the distinct TypeScript approach without duplicating rules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, typescript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100