From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Pavel Volek <Pavel.Volek@ensimag.imag.fr>
Cc: git@vger.kernel.org, Volek Pavel <me@pavelvolek.cz>,
NGUYEN Kim Thuat <Kim-Thuat.Nguyen@ensimag.imag.fr>,
ROUCHER IGLESIAS Javier <roucherj@ensimag.imag.fr>
Subject: Re: [PATCH/RFC] file import functionality for git-remote-mw
Date: Mon, 04 Jun 2012 22:54:11 +0200 [thread overview]
Message-ID: <vpqd35en6h8.fsf@bauges.imag.fr> (raw)
In-Reply-To: <1338837351-8996-1-git-send-email-Pavel.Volek@ensimag.imag.fr> (Pavel Volek's message of "Mon, 4 Jun 2012 21:15:51 +0200")
Pavel Volek <Pavel.Volek@ensimag.imag.fr> writes:
> +sub get_mw_media_pages {
> + mw_connect_maybe();
> +
> + my %pages; # hash on page titles to avoid duplicates
> +
> + # get all pages for mediafiles (they are in different namespace)
> + # only one namespace can be queried at the same moment
> + my $mw_pages = $mediawiki->list({
> + action => 'query',
> + list => 'allpages',
> + apnamespace => get_mw_namespace_id("File"),
> + aplimit => 500,
> + });
This seems to be done unconditionally. Is this reasonable if the user
has explicitely set remote.origin.pages or remote.origin.categories?
Actually, shouldn't this be added to get_mw_pages, next to the code
dealing with these two variables? Perhaps the function should be
split into multiple functions, along the lines of:
sub get_mw_pages {
mw_connect_maybe();
my %pages;
if (@tracked_pages) {
$user_defined = 1;
get_mw_tracked_pages(\%pages);
}
if (@tracked_categories) {
$user_defined = 1;
get_mw_tracked_categories(\%pages);
}
if (!$user_defined) {
get_mw_all_pages(\%pages);
}
return values(%pages);
}
And your code would need to take these 3 options into account.
> +sub get_all_mw_pages() {
> + my @pages = get_mw_pages();
> + my @media_pages = get_mw_media_pages();
> + push(@pages,@media_pages);
Space after comma.
> +# Returns MediaWiki id for a canonical namespace name. Ex.: "File", "Project".
> +sub get_mw_namespace_id() {
> + mw_connect_maybe();
> + my $name = shift;
> + my $query = {
> + action => 'query',
> + meta => 'siteinfo',
> + siprop => 'namespaces',
> + };
> + my $result = $mediawiki->api($query);
It may make sense to cache the result, to avoid querying the API
multiple times if you call the function more than once. We can even
cache this in a configuration variable as the namespace identifiers are
unlikely to change for a given wiki.
> + if (!defined($file)){
Space between ) and { please.
> + my @prefix = split (":",$page_title);
Space after , please.
> + if ($prefix[0] eq "File" || $prefix[0] eq "Image") {
> + # check if there is a corresponding mediafile with the same timestamp => it is page
> + # for new verion of the file (not only for new version of the description of the file)
> + # => download corresponding file version
Don't make long lines like this. In general, we avoid lines longer than
80 characters (or even a bit less), these are >100 and the following are
worse.
Long lines are usually an indication that you did not structure your
code into functions, and this diagnosis seems to apply here.
> + my ($imageid,$imageinfo) = each ( %{$result->{query}->{pages}} );
Space after ",".
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
prev parent reply other threads:[~2012-06-04 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 19:15 [PATCH/RFC] file import functionality for git-remote-mw Pavel Volek
2012-06-04 20:54 ` Matthieu Moy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vpqd35en6h8.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=Kim-Thuat.Nguyen@ensimag.imag.fr \
--cc=Pavel.Volek@ensimag.imag.fr \
--cc=git@vger.kernel.org \
--cc=me@pavelvolek.cz \
--cc=roucherj@ensimag.imag.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).