projectwallace / projectwallace/css-analyzer
store only locations, not string values
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 366
- Forks
- 15
- Avg merge
- 3h 23m
- Merged PRs (30d)
- 3
Description
I can think of two major use cases where I think it's most useful to no longer include substrings as aprt of the result:
- Showing the reports on https://www.projectwallace.com/analyze-css
- Storing the analysis report in a database as plain numbers
The reason we don't need or even want to have the strings is that we can always get them on demand when we need them. For the webpage for example, we can get the string values only for the items we are rendering on screen and leave out the rest. This will lead to a messive memory reduction, making analysis and displaying a bunch faster.
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 files, tests, or entry points are named. Start by tracing how analysis results are assembled and stored, then define which location data replaces string values and verify that reports can still retrieve strings on demand while using less memory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- data, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100