Wrote another batch of #iocaine3 docs: documented most of the matchers, and logging, and standard language runtime library extensions.
Some hard parts still remain, but we're inching closer.
Discussion
Loading...
Post
A'ight! Lets see how far I can get today.
So far, so good. Wrote docs for the Roto-specific dynamic value hacks, documented Request, and I still have some spoons left. Lets see what else I can do today...
The decide() and output() functions should be reasonably easy. I can do that tomorrow. Should be looking at something more... complex today, to get it out of the way.
Request construction is missing, but I can postpone that, because that's only needed when writing tests. If the that part of the documentation is missing, that won't block the 3.0 release. I aim to document testing too, but it's not required.
I have to document ASN & GeoIP stuff... that's not too bad, but perhaps worth doing today.
There's file loading, parsing, and file formats. Not hard, but annoying.
And the big part is garbage generation & templates. I really should get some of that out of the way tonight.
Then we have response generation and metrics.
Fuck, that's still a lot. But I want to release on Friday, so... I guess it is coffee time.
Garbage generators are documented, so are metrics. I'll throw in decide() and output() too.
That will leave Response, templating, file loading & parsing, and ASN & GeoIP matchers 'till tomorrow.
Should be doable! I can dish out file loading & parsing, ASN & GeoIP in the morning, and response & templating at night, then cut the release.
I think I'll drop the draft status from the scripting docs before going to bed tonight.
1 more replies (not shown)
@algernon You might be happy to hear that I'm currently working on lists for Roto, which hopefully allow you to remove some of the extensions you made for Roto.
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled