Improve plugin backward compatibility #4716
Merged
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.
Background
Legacy zipped plugins don't load on 0.4.1, and instead emit a "plugin not configured" warning. The reason appears to be the move from class-based config keys to directory-based config keys.
This PR enables class-based config keys for zipped plugins, which allows legacy plugins to load.
Changes
Updated the code that checks whether a zipped plugin is configured to do so within the plugin load loop, where the class name is available, and updated the emitted debug and warning logs.
Documentation
No change to docs as this is the legacy behavior.
PR Quality Checklist