◊(Local Yarn Code "View Ticket")

04:30 Closed ticket [8ad56020]: Refactor listing/query functions plus 3 other changes artifact: 17d1b4f8 user: joel
Refactor listing functions (see [8ad560204]) check-in: 3be7a3ab user: joel tags: trunk
Revise markup used for short listings (see [8ad560204f7a5c94]); bring back preheat-series check-in: eff5c85d user: joel tags: trunk
07:22 Ticket [8ad56020] Refactor listing/query functions status still Open with 3 other changes artifact: 2cc63411 user: joel
21:49 Ticket [8ad56020]: 4 changes artifact: dc20dd0b user: joel
21:49 New ticket [8ad56020]. artifact: f03f3b78 user: joel

Ticket Hash: 8ad560204f7a5c94691355d4572fa2dca544d849
Title: Refactor listing/query functions
Status: Closed Type: Aesthetic Improvement
Severity: Minor Priority: Immediate
Subsystem: Resolution: Open
Last Modified: 2020-02-20 04:30:35
Version Found In:
User Comments:
joel added on 2020-02-14 21:49:08:

Currently there are three functions <listing-short>, <listing-full> and <listing-excerpt> and you pass them the query-generating function itself (articles or articles+notes), rather than passing an expression using those functions which produces the query.

The only reason we need three separate functions is the different treatment needed for <listing-short>. The markup stored in the listing_short column is contained in an <li>, so <listing-short> needs to return the concatenated HTML wrapped in a <ul> tag. If the markup were changed so that no such special treatment were needed, we could switch to a single listing function, with usage like this:

◊(collate (articles+notes 'short))

joel added on 2020-02-20 04:30:35:

Finished in [3be7a3ababaccdb3]