chore(logging): demote every logger.info to debug - #387
Merged
Conversation
All 240 info-level calls were tracing: queries issued, documents found, retry attempts, key matches. In a production build (min level info) they all printed to the user's console. They are debug now, which the development build still shows and production hides. The logger doc says what each level is for so the next call lands at the right one.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
2 tasks
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.
Summary
logger.infocall inapp/,components/,hooks/,lib/andcontexts/becomeslogger.debug. There were 240 across 38 files; all of them were tracing (queries issued, documents found, retry attempts, key matches, sync progress), none was an operator-facing event.info, so until now every one of these printed to the user's browser console. Development builds (min leveldebug) still show them;NEXT_PUBLIC_LOG_LEVEL=debugshows them anywhere.lib/logger.tsnow documents what each level is for so the next call lands at the right one.warnanderrorare untouched.Mechanical: one
sed-style replace, no argument or message changes. Nothing ine2e/or the unit specs asserts on log output.Part of the anti-slop cleanup series (after #370–#386).
Test plan
npm run lint(zero warnings),tsc --noEmit,npm run test,npx knip,npm run buildall green locallyNEXT_PUBLIC_LOG_LEVEL=debugbrings the tracing back🤖 Generated with Claude Code