From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: GitLab integration take two, light edition
Date: Tue, 08 Sep 2020 09:58:28 -0700 [thread overview]
Message-ID: <871rjc6w97.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87sgbtzec4.fsf@tullinup.koldfront.dk>
Adam Sjøgren <asjo@koldfront.dk> writes:
[...]
> (let ((milestone (cdr (or (assoc "milestone" issue) '("default" . nil))))
> (state (cdr (or (assoc-string "state" issue) '("default" . "unknown"))))
> (labels (cdr (or (assoc-string "labels" issue) '("default" . nil)))))
> (widen)
> (message-goto-eoh)
> (when milestone
> (insert "GitLab-Milestone: " (cdr (or (assoc-string
> "title" milestone) '("default". "unknown"))) "\n"))
This is all looking good, though there's some refactoring you could do
here (there's always refactoring that could be done) -- you've already
guarded against no milestone in the let, then you're checking "(when
milestone", which will always be true now, and then you do the guard all
over again in the body. I'm know you're still in the middle of whacking
this all together, but I thought it might be worth mentioning. In
general, the repetition of the
(cdr (or (assoc-string ..) '("default" . nil)))
pattern all over the place is a good indication that there's a cleaner
approach.
[...]
>>> No, I just don't know (e)lisp, neither the vocabulary of functions nor
>>> the idioms :-)
>>
>> Could have fooled me, you do pretty well with bug-hunting on this list!
>
> That's just experience, which is much easier than knowledge.
Hmm, that's debatable! But I take your point.
next prev parent reply other threads:[~2020-09-08 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 21:15 Adam Sjøgren
2020-08-29 18:45 ` Eric Abrahamsen
2020-09-06 17:58 ` Adam Sjøgren
2020-09-06 21:48 ` Eric Abrahamsen
2020-09-06 22:22 ` Eric Abrahamsen
2020-09-07 17:28 ` Adam Sjøgren
2020-09-08 16:58 ` Eric Abrahamsen [this message]
2020-09-08 17:28 ` Adam Sjøgren
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rjc6w97.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.org \
/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.
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 NNTP newsgroup(s).