From: "amirouche@hypermove.net" <amirouche@hypermove.net>
To: "Clément Lassieur" <clement@lassieur.org>
Cc: Guix-devel <guix-devel@gnu.org>,
Tatiana Sholokhova <tanja201396@gmail.com>
Subject: Re: Web interface pushed
Date: Mon, 30 Jul 2018 09:38:53 +0200 [thread overview]
Message-ID: <3afd-5b5ec080-1-6a567300@3565601> (raw)
In-Reply-To: <87r2jlbsq3.fsf@lassieur.org>
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
Hi
On Monday, July 30, 2018 00:08 CEST, Clément Lassieur <clement@lassieur.org> wrote:
Hi Tatiana,
So, I did the pagination review and I pushed your work tonight. :-)
I added checks to avoid crashes when the table is empty (FIRST and LAST
expect non-empty lists).
I modified a few minor things too:
- the commit message, so that it matches our convention
- the indentation
- I removed code comments, trailing '\' in SQL queries, useless
newlines, useless exports
- I renamed a few things (e.g. thing-list with things, %pagesize with
%page-size)
- I replaced (+ 1 x) with (1+ x)
- I used string-join to avoid long strings
- I used FIRST instead of CAR when used with LAST (for more consistency,
but it's the exact same thing)
- I replaced FIRST and LAST with BUILD-ID and BUILD-STOPTIME, so to make
it more furure-proof and easier to understand
- I used a format string for RESPOND-HTML (to avoid "\"\"")
- I finally opted for a non-parameter %page-size (yes, I changed my mind
:-), I just didn't see any reason to use one)
- I removed ('page (string->number param)) from REQUEST-PARAMETERS (I
think it was useless)
- I added a missing copyright header
And that's all!
Thanks for this work, it'll be very useful. Don't hesitate send new
patches to improve it!
Best regards,
Clément
How can I test?
[-- Attachment #2: Type: text/html, Size: 1622 bytes --]
next prev parent reply other threads:[~2018-07-30 7:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 22:08 Web interface pushed Clément Lassieur
2018-07-29 23:46 ` Ludovic Courtès
2018-07-30 12:45 ` Pjotr Prins
2018-07-30 13:26 ` Ricardo Wurmus
2018-08-01 19:47 ` Tatiana Sholokhova
2018-08-02 6:53 ` Clément Lassieur
2018-08-02 16:00 ` Gábor Boskovits
2018-08-02 16:49 ` Clément Lassieur
2018-08-02 18:48 ` Gábor Boskovits
2018-08-02 19:21 ` Amirouche Boubekki
2018-08-02 20:16 ` Clément Lassieur
2018-08-02 18:13 ` Amirouche Boubekki
2018-08-02 20:17 ` Clément Lassieur
2018-08-03 13:53 ` Ricardo Wurmus
2018-08-04 21:53 ` Tatiana Sholokhova
2018-08-04 22:03 ` Ricardo Wurmus
2018-08-07 21:33 ` Tatiana Sholokhova
2018-08-09 9:17 ` Clément Lassieur
2018-08-09 19:59 ` amirouche
2018-08-09 20:46 ` Ricardo Wurmus
2018-08-10 5:01 ` Gábor Boskovits
2018-08-10 9:10 ` Clément Lassieur
2018-08-11 16:38 ` Ricardo Wurmus
2018-07-30 7:38 ` amirouche [this message]
2018-07-30 9:11 ` Clément Lassieur
2018-07-30 9:23 ` Alex Sassmannshausen
2018-07-30 9:41 ` Nils Gillmann
2018-07-30 12:08 ` Ricardo Wurmus
2018-07-30 12:14 ` Gábor Boskovits
2018-07-30 14:10 ` Hartmut Goebel
2018-07-30 16:02 ` Clément Lassieur
2018-07-30 18:43 ` Amirouche Boubekki
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: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3afd-5b5ec080-1-6a567300@3565601 \
--to=amirouche@hypermove.net \
--cc=clement@lassieur.org \
--cc=guix-devel@gnu.org \
--cc=tanja201396@gmail.com \
/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://git.savannah.gnu.org/cgit/guix.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).