Cached TTD coverage analysis result should be saved to different files
Open
Nobody has claimed this yet.
enhancement
Impact: Medium
TTD
- Dominant language
- C++
- Stars
- 331
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
maybe a UUID or sth, and then save the identifier into the analysis database as metadata
The TTD analysis dialog should also check the existence for this file, and let the user know about it
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 locating the TTD coverage analysis cache handling, the analysis database metadata, and the TTD analysis dialog. Trace how a cached result is saved and how the dialog checks for it. Done means cached results use distinct identifiers recorded as metadata and the dialog reports when the corresponding file exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools, reverse-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100