Clarify logger fallback contract and add direct fallback-handler coverage#6590
Merged
Conversation
4 tasks
Copilot
AI
changed the title
[WIP] Refactor duplicate logger fallback error handlers
Clarify logger fallback contract and add direct fallback-handler coverage
May 27, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR documents the “degraded mode” contract for logger initialization error handlers (fallback vs. strict behavior) and adds focused unit tests to ensure the concrete fallback handlers continue to return usable loggers with the expected fallback state.
Changes:
- Document
loggerErrorHandlerFunccontract: fallback-capable handlers return(logger(useFallback=true), nil), strict handlers return an error. - Clarify
initLoggerdocs for per-logger fallback modes (includingToolsLogger). - Add direct unit tests for
handleFileLoggerError,handleMarkdownLoggerError, andhandleToolsLoggerError.
Show a summary per file
| File | Description |
|---|---|
| internal/logger/fallback_handlers_test.go | Adds direct tests asserting fallback handlers return degraded loggers with useFallback=true. |
| internal/logger/common.go | Documents the fallback/strict contract and clarifies initLogger fallback semantics per logger type. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 3
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
This was referenced May 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The logger package already centralizes initialization through
initLogger, but the fallback handlers for file, markdown, and tools loggers shared the same degraded-mode contract without documenting it explicitly. This change makes that contract explicit and adds direct coverage for the concrete handlers so fallback semantics do not drift.Fallback contract
loggerErrorHandlerFuncas the boundary for degraded-mode behavior:useFallback=trueandnilerrorinitLoggerdocs, includingToolsLoggerFocused handler coverage
handleFileLoggerErrorhandleMarkdownLoggerErrorhandleToolsLoggerErrorExample