projectwallace / projectwallace/stylelint-plugin
analyze anti-patterns
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 0
- Avg merge
- 4h 25m
- Merged PRs (30d)
- 4
Description
Pitched by @Yolijn: if you check for a feature in @supports, that declaration needs to come back somehwere in the CSS within the supports block. Because, if it doesn't, it's somewhat of an anti-pattern. There's some nuances to this, like the use of not, but it's a fair argument and we could totally build something to detect anti-patterns.
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
The issue names CSS @supports blocks but no files, tests, or entry points. Start by locating the plugin's existing rule structure and determine the expected behavior for declarations inside @supports, including the noted use of not; done should include a decided anti-pattern definition and coverage for it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100