Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Add `info` or `details` command to see pod's details #166

Closed
yas375 opened this Issue · 3 comments

2 participants

@yas375

Hi, everyone!

I think it will be helpful to see pod details if needed. For example to see homepage url about some pod which you just found with search command. Also there will be printed all information about pod from spec.

What do you think? Which command name is better? If you agree with me, than I will do it in next few days and will send you pull request.

@alloy
Owner

I think it's a great idea to show more info. However, I wonder if we really need a new command for it, instead of just showing it in the search output. Could you create a mockup of the info you would like to see?

Also see #164 regarding subspec info.

@yas375

Yes, it could be added to search results. But we shouldn't add much more fields there. Because if there are a few search results than it will be too much info. First example:

$ pod search restkit --subspecs

==> RestKit (0.9.3)
    RestKit is a framework for consuming and modeling RESTful web resources on iOS and OS X.'
    Homepage: http://www.restkit.org
    Source: https://github.com/RestKit/RestKit.git

    Sub Specs:
    - RestKit/Network
    - RestKit/ObjectMapping
    - RestKit/ObjectMapping/JSONKit
    - RestKit/ObjectMapping/XML
    - RestKit/ObjectMapping/CoreData

Firstly I add just homepage to this listing, but after that I try to open it and at now restkit.org doesn't respond. Than I need to know source code repo to open it instead. That's why I added here both links.

But now I need only this info, but somebody may be interested in other info from spec now or later. I think it will be easier to show this info in a separate command, not in search results.

BTW: I think even info about subspecs better to show not in search results. Because there are could be lots of information.

resume
If you decide to add at now this info to search results - ok, I still could do it and send you pull request.

thanks

@alloy
Owner

But now I need only this info, but somebody may be interested in other info from spec now or later. I think it will be easier to show this info in a separate command, not in search results.

BTW: I think even info about subspecs better to show not in search results. Because there are could be lots of information.

While I agree with you that it could get messy at some point, I don’t think we’re at that point yet, so let’s keep it simpler until then (people like to remember just a few commands :), in general), at which point it's just a matter of moving the code to a new command.

If you decide to add at now this info to search results - ok, I still could do it and send you pull request.

Yes, please do create a pull request for adding it to the search results!

There’s currently no method on Specification yet to get a list of all subspecs, but I can add that tonight.

Thanks

@alloy alloy closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.