Vector35 / Vector35/binaryninja-api
Improved Reporting Interfaces
Open
Nobody has claimed this yet.
Component: UI
Effort: Medium
Impact: Medium
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
What is the feature you'd like to have?
I would like to have better reporting interfaces that include the following:
- "Reports" pane
- Reports need to be saved to the database
- Reports need to be in a list where people can select from them
- Reports should probably have some idea of who generated them
- Reports should be exportable
Additional Information:
This is a feature that will enable Sidekick to work more fluidly.
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
The issue names no files, tests, or entry points, so start by locating the existing reporting and Sidekick-related interfaces in the project. Define the scope for a Reports pane, database persistence, report selection, generator attribution, and export before implementation. Done should cover each listed reporting capability with clear validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools, reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100