Add logger specs for debug/file logging and picker failure behavior #436

New issue

Closed

opened 2026-04-26 23:33:05 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-04-26 23:33:05 +00:00

Problem

Current logger tests cover fast-event scheduling vs immediate notify, but they do not cover the debug/file logging contract or how picker failure details should be surfaced. That leaves the logging issue under-specified and makes refactors riskier.

Proposed solution

Add focused specs for:

vim.g.forge.debug = true
vim.g.forge.debug = "/path/to/log"
picker failure paths that should preserve and surface real request/decode details

Notes

root tracker: #170

## Problem Current `logger` tests cover fast-event scheduling vs immediate notify, but they do not cover the debug/file logging contract or how picker failure details should be surfaced. That leaves the logging issue under-specified and makes refactors riskier. ## Proposed solution Add focused specs for: - `vim.g.forge.debug = true` - `vim.g.forge.debug = "/path/to/log"` - picker failure paths that should preserve and surface real request/decode details ## Notes - root tracker: #170