Vector35 / Vector35/binaryninja-api
Change Plugin Load Order So User Developed Plugins Can Access Official Plugin APIs
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 change the plugin load order to the following:
- Core
- Core UI
- Official
- Community
- Local
Is your feature request related to a problem?
Today, the load order is such that a local or community plugin is loaded before the official and core ui plugins. Therefore they cannot import from those plugins. The main problem in this case is Sidekick scripting API is not available for import in python plugins.
Are any alternative solutions acceptable?
No sure, but I will try to hack something b/c I really need this.
Additional Information:
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 tracing the plugin discovery and initialization entry points that determine Core, Core UI, Official, Community, and Local ordering; the issue names no source files or tests. Done means user-developed Python plugins can import the official and Core UI APIs, with the requested order verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, reverse-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100