Welcome the channel on the development of Cro, a set of libraries for building reactive distributed systems, lovingly crafted to take advantage of all the Raku Programming Language has to offer (cro.services). This channel is being logged for historical purposes.
Set by lizmat on 24 May 2021.
00:14 lizmat_ joined 00:18 lizmat left 00:34 patrickb left 05:42 Xliff left 05:52 Xliff joined 06:28 Xliff left, Xliff_ joined
Xliff_ How do I get the raw JSON from request to a JSON endpoint using Cro::HTTP::Client? 07:38
09:33 Geth joined, lizmat_ left, lizmat joined
jnthnwrthngtn Xliff_: $resp.body-text instead of $resp.body 10:22
(Or $resp.body-blob if you want it ever less cooked :)) 10:23
Xliff_ jnthnwrthngtn: Thanks! 10:56
lizmat bumped Cro to 0.8.7 and fixed my first Nil warning thanks to the new more precise message 14:13
sadly, I'm still seeing: Use of Nil in string context
in block at EVAL_9 line 200
passing by... maybe with the initial template parsing? 14:14
15:36 patrickb joined 16:24 AlexDaniel left, CIAvash left 16:35 AlexDaniel joined 16:39 ecocode__ left, SmokeMachine left 16:40 kawaii_ left 16:41 ecocode__ joined 16:42 SmokeMachine joined 16:43 kawaii_ joined 16:45 CIAvash joined 17:01 AlexDaniel left 17:46 lizmat_ joined 17:47 lizmat_ left, lizmat_ joined 17:49 lizmat left, lizmat_ left, lizmat joined 17:53 patrickb left 18:20 patrickb joined
lizmat logs.liz.nl now running on Cro 0.8.7 21:29
21:29 AlexDaniel joined
lizmat so this template snippet: 21:31
<?{ .channel ne $c }>
<li id="<$c>">
is generating a warning on the last line 21:32
the only way I can think of this, is that $is-home is Nil, but that shouldn't be an issue in a condition, should it ?
it cannot be $c. because then I'd also get a warning on the 2nd line of that snippet 21:33
lizmat is confused
two other warnings point to lines that do not have any variable in them, such as "</div>" 21:34
lizmat calls it a day 21:35