projectwallace / projectwallace/css-analyzer
🗂️ analyze multiple input files
Open
Nobody has claimed this yet.
✨ enhancement
- Dominant language
- TypeScript
- Stars
- 366
- Forks
- 15
- Avg merge
- 3h 23m
- Merged PRs (30d)
- 3
Description
This would be useful, because highlighting a specific node could be done on a per-file basis.
Need to figure out whether to concat all input css as a single string, then analyze; or analyze per input and then combine the stats.
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 file, test, or entry point is named in the issue. Start by locating the analyzer's input handling, then resolve whether multiple CSS files are concatenated or analyzed separately; done means supporting multiple inputs while retaining per-file node highlighting and combined statistics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- analytics, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100