Validate keys.log.filter #661

New issue

Closed

opened 2026-05-09 00:46:38 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-05-09 00:46:38 +00:00

Owner

Problem

keys.log.filter is defaulted, documented, and used, but config validation omits it.

Evidence:

default: lua/forge/config.lua:174
docs: doc/forge.nvim.txt:328
validator only checks next_step, prev_step, and refresh: lua/forge/config.lua:509

A malformed configured filter key can reach runtime keymap setup instead of failing during config validation.

Expected

Validate keys.log.filter using the same key-or-false rule as the other log keys.

Context

Found during release-preview readiness audit. Remote Forgejo CI cannot currently be awaited because the Spark runner is down; use local verification for the fix.

## Problem `keys.log.filter` is defaulted, documented, and used, but config validation omits it. Evidence: - default: `lua/forge/config.lua:174` - docs: `doc/forge.nvim.txt:328` - validator only checks `next_step`, `prev_step`, and `refresh`: `lua/forge/config.lua:509` A malformed configured filter key can reach runtime keymap setup instead of failing during config validation. ## Expected Validate `keys.log.filter` using the same key-or-false rule as the other log keys. ## Context Found during release-preview readiness audit. Remote Forgejo CI cannot currently be awaited because the Spark runner is down; use local verification for the fix.

barrettruth added the

bug

label

2026-05-09 00:46:38 +00:00

barrettruth referenced this issue

2026-05-09 00:47:16 +00:00

Tracker: release-preview readiness follow-up #667

barrettruth referenced this issue from a pull request that will close it,

2026-05-09 00:54:14 +00:00

Validate log filter key config #669

barrettruth closed this issue

2026-05-09 02:39:02 +00:00