feat: allow hiding code location in console log output - #9
Merged
cuinixam merged 1 commit intoSep 15, 2026
Merged
Conversation
cuinixam
requested changes
Sep 15, 2026
setup_logger now takes show_code_location. It is off by default, which keeps the console output of every existing caller unchanged. The log file is not affected. A log file is read for debugging, so it keeps the code location in all cases. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
TheRedSwabian
force-pushed
the
feature/configurable-log-code-location
branch
from
September 15, 2026 07:17
72ec616 to
d83679b
Compare
cuinixam
approved these changes
Sep 15, 2026
This branch was successfully deployed
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.
setup_logger now takes show_code_location. It is off by default, which keeps the console output of every existing caller unchanged.
The log file is not affected. A log file is read for debugging, so it keeps the code location in all cases.
The format moved into a new public function create_log_format, so a consumer that adds its own sink can reuse it instead of copying the string.
Unrelated: the .gitignore entry for *.stackdump catches the crash dumps Git Bash drops on Windows. Say the word and I take it out.