Skip to content

Conversation

@TheBrambleShark
Copy link
Contributor

@TheBrambleShark TheBrambleShark commented May 31, 2025

Fixes #9
Fixes #2
Fixes #8

Adds a couple builder types which was necessary for caching the plugins before initializing them.

Additionally, the plugin service now no longer requires an Option<PluginServiceOptions> (#2) and allows multiple plugins per assembly (#8). Currently it just adds all of the plugins from the assembly that match the provided predicate.

@TheBrambleShark
Copy link
Contributor Author

TheBrambleShark commented May 31, 2025

I'll get these resolved here shortly. Just wanted to get my code pushed.

@TheBrambleShark
Copy link
Contributor Author

@Nihlus Can you look into why the build is failing? It seems to be a pipeline issue.

@MazeXP
Copy link
Contributor

MazeXP commented Jun 11, 2025

I might not be Nihlus, but the reason for the CI failure is quite simple.
This project does not contain any tests at all therefore no coverage files can be generated, which the Coverage step requires.
#11 will fix the issue

@TheBrambleShark
Copy link
Contributor Author

Thanks Maze. I'll push an empty commit to kick off the checks again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Static Plugin Initializer Allow Multiple Plugins Per Assembly Make options not required for when following the readme.

2 participants