Compressed snapshots
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Describe the Feature You Want
We would like to attach the snapshots as part of issues, and it would be great if they were as small as possible. It's not like the snapshots have any value without the "viewer", since, although plain json files, they are not natively "viewable"
Current Behavior
Well, now, a 1MB json file is compressed down to 70k and although we could manually compress it and then download and decompress, it would be much more efficient if the viewer was working directly with the compressed format.
Why Do You Want This?
Already described above!
Thanks!
Contributor guide
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 locating the snapshot generation and viewer entry points, since the issue does not name specific files or tests. Trace how JSON snapshots are produced, attached, downloaded, and opened by the viewer. Done means snapshots can use the compressed format while the viewer opens them directly, preserving the existing snapshot contents.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100