43081j / 43081j/eslint-plugin-wc
define-tag-after-class-definition: ignore abstract classes by default
Open
- Dominant language
- TypeScript
- Stars
- 113
- Forks
- 19
- Avg merge
- 3h 14m
- Merged PRs (30d)
- 2
Description
It'd be nice to ignore abstract classes by default.
Yes, I know you have to use @typescript-eslint/parser as parser, but please. :P
edit:
Oh, you already depends on typescript-eslint, then it's easy.
Contributor guide
No contributing guide indexed for this repository
Research direction
Look at the rule 'define-tag-after-class-definition' in the plugin's source code. Understand how it currently detects class definitions and how to identify abstract classes using the TypeScript parser. Modify the rule to skip abstract classes by default, and test with a TypeScript file containing an abstract class.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100