-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subcommand plugins via cocoapods_plugin.rb
file
#3
Conversation
Any CLAide Command can load subcommand plugins by setting the Command.plugin_prefix for the command. Installed gems with a file named `<plugin_prefix>_plugin.rb` will be loaded via that file. Convention is to require the actual command implementation in the plugin file. If Command.plugin_prefix is not set, no attempt is made to load any plugins.
Perfect, thanks again! |
Subcommand plugins via `cocoapods_plugin.rb` file
@orta LOL! |
I also have a plugin! https://github.com/irrationalfab/cocoapods-docs |
👍 |
@leshill - would you be interested in doing us a writeup on how to make a plugin as a post on the cocoapods blog? |
Hi @orta, Thanks for the offer, but I cannot. And honestly, it is very easy to do so. A blog post showing how to write your own subcommands would be great; and making the gem a plugin would be part of that? |
Yeah, that sounds like exactly the kind of thing I would like to have. Cause we need to have docs for it somewhere. |
I have added some bells and whistles in f925edc |
Good idea! |
@irrationalfab 👍 |
Any CLAide Command can load subcommand plugins by setting the Command.plugin_prefix for the
command. Installed gems with a file named
<plugin_prefix>_plugin.rb
will be loadedvia that file. Convention is to require the actual command implementation in
the plugin file.
If Command.plugin_prefix is not set, no attempt is made to load any plugins.
PR CocoaPods/CocoaPods#1563 on CocoaPods to set the
Command#plugin_prefix
.The
open
command has been updated here https://github.com/leshill/open_pod_bay/tree/new_style