agessaman cc6ca00b4e docs(keywords): say the newline escape is a backslash, not a slash (#277) ...

The report used /n and got two literal characters. The escape works the same in
every keyword path — I checked the test command's template engine too — so the
defect is that the instructions never said "backslash" and used `test` as their
example, which is the one keyword a built-in command owns. That command renders
through a different engine and silently drops the mesh-info placeholders listed
in the same block.

Also documents the configparser continuation form, which needs no escape, and
corrects two packet-capture examples that still showed a naive local timestamp
where the bot has published UTC with a Z suffix since v1.0.0 (#276).

2026-09-20 10:58:17 -07:00

..

__init__.py

Update configuration handling and validation for bot sections

2026-02-12 19:23:35 -08:00

test_keyword_escapes.py

docs(keywords): say the newline escape is a backslash, not a slash (#277)

2026-09-20 10:58:17 -07:00