projectwallace / projectwallace/css-code-quality
Deduct points for using too many shorthands
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 155
- Forks
- 4
- Avg merge
- 3h 34m
- Merged PRs (30d)
- 1
Description
Shorthands are risky and spec authors sometimes actually regret them when for example you can't add new props to the animation shorthand because it's already "a dumpster fire of parsing".
Contributor guide
No contributing guide indexed for this repository
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 reviewing the existing quality guards and the code that parses CSS declarations or shorthand properties. Determine how a shorthand-count guard would fit the current scoring model and what threshold and deduction are needed; done means the guard is represented in the calculated CSS quality score.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100