Post
I'm currently writing #Fennel examples, and this is delightful. I even managed to make the decide function even more beautiful than it was!
(local ruleset [is-in-ai-robots-txt?
default])
(fn decide [request]
(accumulate [outcome nil
_ f (ipairs ruleset)
&until (not= outcome nil)]
(f request)))
This is perfection.
I'm currently writing #Fennel examples, and this is delightful. I even managed to make the decide function even more beautiful than it was!
(local ruleset [is-in-ai-robots-txt?
default])
(fn decide [request]
(accumulate [outcome nil
_ f (ipairs ruleset)
&until (not= outcome nil)]
(f request)))
This is perfection.
From nothing to running iocaine + Caddy with ai.robots.txt's robots.json and a few metrics as a starting point.
Contains #Roto, #Lua, and #Fennel - and a few tests too, for each.
Ok, a short break, then I'll finish the "Lua in iocaine" reference guide, then maybe tweak the landing page... but after the reference guide, the most important parts of my iocaine TODO list are taken care of, the rest is optional.
Halfway through the Lua-in-iocaine reference guide, will likely finish it today after bedtime stories.
If not, tomorrow! And even if not tomorrow, this is not a blocker for the 2.5.0 release.
One other bug (Lua runtime errors not properly propagated up) on the other hand, is.
That Lua runtime error not propagating bug? That only affects the test runner. It is properly propagated otherwise.
Turned out to be a very easy fix.
Noticed the problem while writing the Getting Started guide: I made a typo in one of the Lua tests, and the testsuite was failing, and I had no output whatsoever. Took a bit of trial and error to spot the typo and fix it, and that revealed the root problem: runtime errors were silently ignored by iocaine test when used with the Lua/Fennel engine.
A space for Bonfire maintainers and contributors to communicate
