Correctly load plugins, even in sub-directories.#447
Correctly load plugins, even in sub-directories.#447felabrecque wants to merge 3 commits intoexposedev:devfrom
Conversation
|
Anything missing for this PR to be merged ? |
mechelon
left a comment
There was a problem hiding this comment.
While I like the idea - especially with cloning custom plugins with git, a few thoughts on this:
-
The changes break backward compatibility for existing plugin setups. Specifically, custom plugins in
~/.expose/pluginsare no longer detected, e.g. created byexpose make:plugin. -
For a fundamental change to the plugin system, we need:
- Unit tests to verify both new and existing functionality
- Updated documentation explaining the new plugin requirements and structure
- Preservation of backward compatibility for existing plugin setups
I can work on that next week. Once the code is completed. I will add the tests and documentation. Didn't want to spend time on that if the PR would have been rejected. |
|
@mechelon I don't see how plugins in the I didn't changed which folders are scanned. I only added some additional checkup:
this shouldn't have any impact on existing plugins. And Can you explain to me what I did wrong so I can fix it ? |
Previously, any files in ~/.expose/plugins directory was loaded as a plugin.
Now, README.md files are excluded.
Also, the plugin can be in a sub-folder.
This means we can do something like:
git clone custom-expose-plugin.git
in the plugins folder and it will work