Q, pod suggestion

[kevindawson]

I think you need a POD example to show, attribute usage for module data

do this

use MetaCPAN::Client;
my $mcpan = MetaCPAN::Client->new();
my $mc = $mcpan->module('Digest::MD5');
my $mc_version = $mc->version();

instead of this

use MetaCPAN::Client;
my $mcpan = MetaCPAN::Client->new();
my $mc = $mcpan->module('Digest::MD5');
my $mc_version = $mc->{data}{version};

ps it tock me a while to figure the above out from the code, when using Data-Printer you can see the exported methods for $mcpan->distribution, but not for $mcpan->module

hope the above helps, from a newbe perspective to MC-C

[kevindawson]

labels as 'question' please

[kevindawson]

MetaCPAN::Client::Module  {
    Parents       MetaCPAN::Client::File
    public methods (1) : new
    private methods (0)
    internals: {

and

MetaCPAN::Client::Distribution  {
    Parents       Moo::Object
    public methods (3) : bugs, name, new
    private methods (1) : _known_fields
    internals: {

[xsawyerx]

The documentation clearly says the attributes are those available in MetaCPAN::Client::File. If you go to MetaCPAN::Client::File's documentation (the link to which is automatically generated in metacpan.org), you can clearly see which attributes are available.

Where is the problem, then?

[kevindawson]

if you do

use MetaCPAN::Client;
my $mcpan = MetaCPAN::Client->new();
my $mc = $mcpan->module('Digest::MD5');
p $mc;

you don't see the attributes as you do when you use $mcpan->distribution.
see above.

[tsibley]

That's not a MetaCPAN::Client problem, that's a problem with your preferred data inspector that's easily remedied. Try setting Data::Printer's "class inherited" option to "all", as in https://metacpan.org/pod/Data::Printer#CUSTOMIZATION.

perl -MDDP -MMetaCPAN::Client -e 'p(MetaCPAN::Client->new->module("Digest::MD5"), class => { inherited => "all" })'

[tsibley]

You can set that permanently in your ~/.dataprinter config file.

[kevindawson]

tsibley++

many thanks

I will go and rtfm

hence closing

[xsawyerx]

Thanks, @tsibley and @kevindawson.