Vector35 / Vector35/binaryninja-api
patch file differences
Open
Nobody has claimed this yet.
Component: Core
Component: UI
Effort: Medium
Impact: Low
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Two related features:
- Create a patch diff file so that patches don't have to be applied directly to the original file.
- Show the pending changes between the file on disk and the current version being edited prior to saving it back to disk.
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 or tests. Start by locating the code that applies patches and saves edited files, then trace how on-disk and in-memory versions are represented. Done means both requested behaviors have defined user-visible output and coverage for creating patch files and showing pending changes before saving.
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
- Mostly clear
- Newbie friendliness
- 25/100