[eslint-plugin] Add option to enable casedAttribute but not casedPropertyWithoutAttribute
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21.8k
- Forks
- 1.1k
- Avg merge
- 18h 25m
- Merged PRs (30d)
- 2
Description
### Should this be an RFC?
- [X] This is not a substantial change
### Which package is this a feature request for?
Other/unknown (please mention in description)
### Description
In https://github.com/lit/lit/pull/4516 we're adding a lint rule around attribute names and property names. I think many users, including google's internal codebase, will want the casedAttribute warning but not the casedPropertyWithoutAttribute warning.
### Alternatives and Workarounds
Leave the lint rule disabled entirely for now.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the referenced lit/lit pull request #4516 to understand the casedAttribute and casedPropertyWithoutAttribute warnings and where the eslint plugin defines them. Confirm that the new option can enable the attribute warning independently, then add coverage for both enabled and disabled combinations and run the plugin's existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100