projectwallace / projectwallace/projectwallace.com
Check css analysis of almanac against our own
Nobody has claimed this yet.
- Dominant language
- Svelte
- Stars
- 3
- Forks
- 0
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 11
Description
@tunetheweb gave me this link, which could be quite helpful in discovering differences between how the almanac analyzes CSS vs. we I do it. This should help us discover any shortcomings in our own analysis as well as those in the Almanac.
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 opening the linked Google Sheet and comparing its CSS analysis with Project Wallace's own results. The payload names no source files, tests, or entry points, so first locate the analysis implementation and determine which discrepancies are genuine shortcomings. Done means documenting the differences and identifying the analysis changes needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- analytics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100