projectwallace / projectwallace/projectwallace.com
let /custom-properties use css-analyzer's analysis
Open
Nobody has claimed this yet.
page: custom-property-inspector
platform: code improvement
- Dominant language
- Svelte
- Stars
- 3
- Forks
- 0
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 11
Description
css-analyzer@9.9.0 introduced used/unused/defined/unknown metrics for many named identifiers
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 at the /custom-properties route and inspect how it currently obtains and presents custom-property data. Review css-analyzer@9.9.0's used, unused, defined, and unknown metrics, then verify that the route uses the intended metrics and displays them correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100