Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Plugin loading #855
Ready for merge. Outstanding todo items can be added in subsequent PRs
Plugin installation/distribution system that piggy-backs on composer infrastructure. Follow-up to #849
Available commands for
It's in todo ("ability to refer to plugins by package name (cli only)"). But if this is going to be used to manage non-composer plugins, there's also got to be a way to refer to plugins that are not packages. Since I don't want file names there, it leaves class names as the only choice.
I think it could be made to. Autoloading is functional in phar builds, so as long as interfaces used by plugin is not mangled by
Is it because their base class is prefixed?
One point I'd like to decide before moving further is naming. How do we name this entire thing: "plugins", "extensions", "bundles", something else? "plugins" is currently ambiguous, as it refers both to old plugins as well to this new package based thing. My preference would be keep this named "plugins", add a
5 times, most recently
Jul 13, 2018
muglug left a comment
Got back a little later than intended, I've left some suggestions for documentation.
On a first glance this looks good - would you be able to migrate the plugins in the
Awesome, thanks. I'm going to make this part of a 3.0 release together with the