Allowing plugins to be used as dependencies to other plugins#16
Merged
sylvessa merged 4 commits intosylvessa:feature/plugin-apifrom May 6, 2026
Merged
Conversation
…, make plugin api references possible)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR allows plugins to reference each other as a dependency in .csproj
Changes
Previous Behavior
Previously, you could not easily reference other plugins within your plugin (such as communicating with an API)
Root Cause
Loading dependencies did not account for plugins, meaning it would try to load the same plugin twice
New Behavior
Load() in PluginLoadContext now checks to see if the assembly is already loaded
Fix Implementation
I added a foreach statement that basically loops through the AssemblyLoadContext to make sure the wanted assembly isn't already loaded
AI Use Disclosure
AI was used to guide me through how System.Reflection works and to find the root cause of the problem. The PR is not vibe-coded, and the code is not generated by AI.