1.9 KiB
id, title, status, assignee, created_date, updated_date, labels, dependencies, priority, ordinal
| id | title | status | assignee | created_date | updated_date | labels | dependencies | priority | ordinal |
|---|---|---|---|---|---|---|---|---|---|
| TASK-86 | Include config validation issue details in user notifications | Done | 2026-02-19 17:24 | 2026-02-19 23:18 | medium | 62000 |
Description
When config validation finds non-fatal issues, users should see concise per-issue details in notification body (not only issue count) so they can fix config quickly without checking logs.
Acceptance Criteria
- #1 Startup notification body includes per-issue details (path + message) for config validation warnings.
- #2 Hot-reload validation warning notifications include per-issue details in notification body.
- #3 Notification text remains concise and does not exceed practical desktop notification limits.
- #4 Automated tests cover notification body formatting with detailed issues.
Implementation Notes
Added buildConfigWarningNotificationBody to format concise multi-line warning details (path+message, line limit + overflow count). Startup warnings now use this formatter for desktop notification body. Config hot-reload runtime now emits non-fatal validation warnings via onValidationWarnings(configPath, warnings) and main process surfaces them through desktop notifications. Added tests for formatter output, startup notification body content, and hot-reload warning callback behavior.
Final Summary
Config validation notifications now include concrete issue details in the notification body instead of only a count. Startup and hot-reload warning paths both surface per-issue path: message lines with concise truncation safeguards. Added regression tests covering formatter output and both notification paths.