Vector35 / Vector35/binaryninja-api
Implement `BNAddOptionalPluginDependency` for Python API
Nobody has claimed this yet.
- 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?
Please implement the equivalent to BNAddOptionalPluginDependency for the Python API.
Is your feature request related to a problem?
Two problems:
- If I make a workflow plugin, I want to make sure that I can wait until another workflow plugin has already cloned metaanalysis so that I can then clone metaanalysis.
- If I make any plugin, I want to be able to wait for another official, community, or local plugin to load in the case that I need to import functions, classes, APIs from those plugins.
Are any alternative solutions acceptable?
Will try to hack something, but I don't know of an alternative now.
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 existing BNAddOptionalPluginDependency API and the Python API binding or plugin-dependency entry points in this repository. Compare the current native behavior with the Python-facing API, then define completion as Python plugins being able to wait for the named dependency to load, with coverage for both workflow and general plugin use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- 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