feat(api): add provider failure summaries #86

Merged
barrettruth merged 1 commit from feat/provider-failure-summary into main 2026-04-25 23:55:22 +00:00
barrettruth commented 2026-04-25 23:53:38 +00:00

Problem

Custom providers can parse diagnostics and expose raw output, but they cannot participate in the short failure notification. That makes failure UX harder to extend without pushing format-specific behavior into the compiler.

Solution

Add an optional failure_summary(result, ctx) provider hook, validate and document it, and route failure notifications through it before falling back to the existing generic and :Preview output hint path. Add focused config and compiler tests for one-shot and long-running providers, plus fallback behavior when the hook returns nil or errors.

<!-- Thank you for contributing to Neovim! If this is your first time, check out https://github.com/neovim/neovim/blob/master/CONTRIBUTING.md#pull-requests-prs for our PR guidelines. --> ## Problem Custom providers can parse diagnostics and expose raw output, but they cannot participate in the short failure notification. That makes failure UX harder to extend without pushing format-specific behavior into the compiler. ## Solution Add an optional `failure_summary(result, ctx)` provider hook, validate and document it, and route failure notifications through it before falling back to the existing generic and `:Preview output` hint path. Add focused config and compiler tests for one-shot and long-running providers, plus fallback behavior when the hook returns `nil` or errors.
Sign in to join this conversation.
No description provided.