projectwallace / projectwallace/css-code-quality
compute score based on stylelint errors/warnings
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 155
- Forks
- 4
- Avg merge
- 3h 34m
- Merged PRs (30d)
- 1
Description
Now that we have projectwallace/stylelint-plugin, we can replace most computations and calculate the score based on the amount and types of warnings/errors that stylelint would give. The main downside of that is that stylelint does not run in the browser.
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
No files, tests, or entry points are named. Start by tracing the current score computations and the existing projectwallace/stylelint-plugin integration; determine how warning and error amounts and types should map to scores, while accounting for stylelint not running in the browser. Done means the score uses the intended stylelint diagnostics without losing browser support.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100