hi Renee,

we already support pod fetching (by type) through the module object:
my $pod = MetaCPAN::Client->new->module("Moo")->pod("html");

why was this needed? (i want to understand if there is something we missed)

cheers,
Mickey

Hi Mickey,

with the code you mentioned, an unnecessary request is done. And when you want the pod for the same module twice a second request is done.

Renee

@oalders you were right. I removed "use Test::Fatal"

according to your code, you will still issue a separate request for the same pod for each type.
I can't really see why someone will issue a second request for the same pod+type from the same app - is this a use case you have?
I'm still having hard time seeing the added value here.

yes, for different types you have to do seperate requests as there is no way to get them in one request.

I have a use case where I want the pod but not the other module information. So I'd like to avoid the extra request that is done when I have to write ->module( "modulename" ).

FWIW, when I'm building Pod for iCPAN, I have a similar use case. I already know everything I need to know about the modules -- I just need the Pod. This seems like an elegant way to solve it.

To expand on this, when I'm fetching Pod for everything in 02packages, the additional request would add a fair amount of overhead.

sure, saving on the module fetch is fair enough (i thought the argument was for fetching the pod twice).
I don't object to the PR, just wanted to understand it value better.
the reason I added pod as a method to the module object is part of a bigger effort to connect some dots and get info across the different objects (will probably force me to do some renaming there).
I'll try to release it during the weekend.
Renee - thanks for the contribution.
cheers,
Mickey