Fix plugin loader to correctly activate plugins #92
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.
It fixes a bug on my previous pr.
The bug was caused by the plugin loader not correctly using the plugin_name attribute to identify plugins when matching them with their configurations in config.yaml. Instead, it was using the class name or other identifiers that didn't align with the names specified in the configuration file. This mismatch meant that plugins, especially community plugins, were not being recognized and thus not activated as intended.
Changing the plugin loader to utilize the plugin_name attribute defined within each plugin fixed the problem.
And a typo, thank you @jeremiah-k .