projectwallace / projectwallace/css-analyzer
☂️ Umbrella issue: CSS nesting and AST traversing issues
Open
Nobody has claimed this yet.
✨ enhancement
- Dominant language
- TypeScript
- Stars
- 366
- Forks
- 15
- Avg merge
- 3h 23m
- Merged PRs (30d)
- 3
Description
There's a couple of issues that can be resolved once we put in place an updated method of walking our AST: we need to keep track more of how rules are nested and how that influences rule sizes, complexity etc.
- https://github.com/projectwallace/css-analyzer/issues/320
- https://github.com/projectwallace/css-analyzer/issues/288
- https://github.com/projectwallace/css-analyzer/issues/251
- https://github.com/projectwallace/css-analyzer/issues/267
- Will make it possible to calculate the total complexity of any rule/atrule/declaration based on it's children
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 reading linked issues #320, #288, #251, and #267 to understand the AST traversal and CSS nesting problems. Done means an updated AST walk tracks rule nesting and enables complexity, size, and child-based totals for rules, at-rules, and declarations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100