It took me browsing through a ton of modules, writing a semi-negative review, then accidentally stumbling on Pithub::Base (and deleting the review) before I realized that I actually do NOT have to set user/repo on each submodule and that there is a token attribute that takes an OAuth token.
I think even if the Pithub's synopsis had this extra bit of sample code, it'd save users a lot of confusion and frustration:
my $pit = Pithub->new(
user => $user,
repo => $repo,
token => $oauth_token,
);
$pit->repos->get;
$pit->repos->commits->list;
P.S.: it'd also be interesting to know why the dist is called "Pithub". Perhaps an ABOUT section in the pod could cover that.
It took me browsing through a ton of modules, writing a semi-negative review, then accidentally stumbling on Pithub::Base (and deleting the review) before I realized that I actually do NOT have to set user/repo on each submodule and that there is a
token
attribute that takes an OAuth token.I think even if the Pithub's synopsis had this extra bit of sample code, it'd save users a lot of confusion and frustration:
P.S.: it'd also be interesting to know why the dist is called "Pithub". Perhaps an
ABOUT
section in the pod could cover that.