quicksilver / quicksilver/Quicksilver
Better crash report management
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 2.9k
- Forks
- 291
- PR merge metrics
- No merged PRs in 30d
Description
If the user is not running the latest version of Quicksilver, the crash reporter dialogue should recommend that the user upgrades to the latest version.
To save on bandwidth and work for the devs sifting through the crash reports, it should not offer to upload crash reports unless the user is on the latest version of Quicksilver.
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 Quicksilver's crash reporter dialog and the existing version-check and upload-flow entry points. Trace how the installed version is compared with the latest release; done means older versions are prompted to upgrade and cannot upload crash reports, while the latest version retains the upload option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- objective-c
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100