mirrors/hermes-agent
1
0
Fork 0
mirror of https://github.com/NousResearch/hermes-agent.git synced 2026-07-21 16:18:55 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 7

test(config): update placeholder usage assertion for --force flag

Browse source 
CI caught test_config_set_usage_marks_placeholders failing on this PR's
new usage line ('Usage: hermes config set [--force] <key> <value>' vs
the previous 'Usage: hermes config set <key> <value>').

The usage change is intentional — it documents the --force escape hatch
this PR adds for bypassing schema validation. Update the assertion to
require the placeholder markers and --force keyword without pinning the
exact wording, so future doc tweaks (e.g. wrapping or color codes) don't
re-break this test.

Confirmed locally: 4/4 placeholder tests pass.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Bartok9 2026-05-28 22:42:14 -04:00 • committed by Teknium
parent 70679ada61
commit fd19e8bb48
1 changed files with 9 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

10
tests/hermes_cli/test_placeholder_usage.py
View file

@ -18,7 +18,15 @@ def test_config_set_usage_marks_placeholders(capsys):
assert exc.value.code == 1
out = capsys.readouterr().out
assert "Usage: hermes config set <key> <value>" in out
# The usage line documents the optional --force flag added in #34067
# (schema validation for unknown keys). Placeholder convention is preserved:
# the literal ``<key>`` and ``<value>`` markers must still be present so
# downstream tooling can detect placeholder syntax.
assert "Usage: hermes config set" in out
assert "<key>" in out
assert "<value>" in out
# --force escape hatch must be documented in the usage line.
assert "--force" in out
def test_config_unknown_command_help_marks_placeholders(capsys):