projectwallace / projectwallace/css-analyzer
Allow analysis of inline styles specificity
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 366
- Forks
- 15
- Avg merge
- 3h 23m
- Merged PRs (30d)
- 3
Description
projectwallace.com/analyze-css is capable of scraping inline styles, which means we're not limited to a 3-number specificity tuple ([0,0,0]). We could allow a specific selector name that would be recognised as an inline style, setting the specificity to [1,0,0,0]. This could or maybe should be a configurable option., so other tools could set their own selector preference.
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 analyzer entry point described by projectwallace.com/analyze-css and trace how inline styles are scraped and specificity tuples are produced. Define how the inline-style selector is identified and whether its selector preference is configurable; done means inline styles report specificity [1,0,0,0] without breaking ordinary selectors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100