feat(modules): plugins/modules architecture #14
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.
This pull request includes significant updates to the plugin architecture and documentation, focusing on the addition of a new plugin system and the implementation of a Rust-based plugin for OBS (Open Broadcaster Software). The most important changes include the addition of a new plugin skeleton, the creation of an OBS plugin, and updates to the documentation to reflect these changes.
Module/Plugin Configuration
Inside the
ModuleAction
you can find anVec<ModuleSettings>
property which will holds all information you need tobuild the settings page inside the application. You can think into something which will holds any metadata needed to
perform the module action. E.g:
This will be stored together with the user profile and should be sent to every request arg as
{module}_{settings}
.Imagine that we have two different modules being
Twitch
andOBS
:you would be able to use these informations inside the module actions: