[00:15] *** Geth left [00:15] *** Geth joined [00:20] *** Geth left [00:20] *** Geth joined [00:27] *** [Coke]_ joined [00:29] *** [Coke] left [00:30] *** [Coke]_ is now known as [Coke] [04:48] *** xinming left [04:50] *** xinming joined [13:20] *** Altai-man joined [14:09] *** Altai-man left [14:09] *** Altai-man joined [14:09] *** japhb left [14:38] *** japhb joined [15:45] *** [Coke] left [15:47] *** [Coke] joined [17:44] *** Altai-man left [22:11] ¦ cro-webapp/structural-tags: b26c21341d | (Jonathan Worthington)++ | 4 files [22:11] ¦ cro-webapp/structural-tags: Implement conditional structural tags [22:11] ¦ cro-webapp/structural-tags: [22:11] ¦ cro-webapp/structural-tags: So `">Visit Website` will render the [22:11] ¦ cro-webapp/structural-tags: anchor tag if the condition is true, placing the closing `` as if [22:11] ¦ cro-webapp/structural-tags: it were written prior to the ``. Works for negative conditions [22:11] ¦ cro-webapp/structural-tags: also. [22:11] ¦ cro-webapp/structural-tags: review: https://github.com/croservices/cro-webapp/commit/b26c21341d [22:11] ¦ cro-webapp/structural-tags: 0ead24e74b | (Jonathan Worthington)++ | 5 files [22:11] ¦ cro-webapp/structural-tags: Implement conditional iteration tags [22:11] ¦ cro-webapp/structural-tags: [22:11] ¦ cro-webapp/structural-tags: So that instead of `<@.foo>
  • <$_>
  • `, one can instead write [22:11] ¦ cro-webapp/structural-tags: `<@.foo li><$_>` to achieve the same result. [22:11] ¦ cro-webapp/structural-tags: review: https://github.com/croservices/cro-webapp/commit/0ead24e74b [22:16] jnthnwrthngtn: Given your above commits, what's the new idiom for showing a list *or* showing a replacement of a different type, like

    or so? [23:10] *** melezhik joined [23:18] japhb: If I understand what you mean, it means you'd get to do now: <@.foo li><$_> ... [23:18] Which saves the , , and

    having to be written [23:20] *** melezhik left [23:33] OK, makes sense, thank you. [23:39] I'm pondering that a bare ... (without a condition) could immediately follow a ... (well, whitespace allowed between them) and serve as an "else" [23:40] jnthnwrthngtn: Well, as long as "immediately follow" allows whitespace between, yeah, I like that idea. [23:40] Then it'd be ... and one less mention of the `.foo` [23:41] Although it arguably looks a tad odd :) [23:42] Anyway, sleep time for me o/ [23:46] Good night!