1 - Fork/refactor cocoapods-plugins to be a plugin manager for CLAide based tools.
2 - Use claide-plugins to manage plugins for Danger
3 - Refactor existing cocoapods-plugins to extend from claide-plugins. It would end up quite a bit thinner, and would only have to implement the publish subcommand.
I've created a Plugins::Configuration class that has some defaults for CLAide, and can be overwritten by setting CLAide::Plugins.config with a custom config when you include in your project.
It includes the create, list, and search subcommands, but does not include publish as I'm not yet sure if that is a generic enough action to include in here.
cc/ @AliSoftware @orta @neonichu @segiddins (please add others who may be interested)
Here's the goal.
1 - Fork/refactor cocoapods-plugins to be a plugin manager for CLAide based tools. 2 - Use claide-plugins to manage plugins for Danger 3 - Refactor existing cocoapods-plugins to extend from claide-plugins. It would end up quite a bit thinner, and would only have to implement the
publishsubcommand.I've created a
Plugins::Configurationclass that has some defaults for CLAide, and can be overwritten by settingCLAide::Plugins.configwith a custom config when you include in your project.It includes the
create,list, andsearchsubcommands, but does not includepublishas I'm not yet sure if that is a generic enough action to include in here.cc/ @AliSoftware @orta @neonichu @segiddins (please add others who may be interested)