Skip to content

chore(logging): demote every logger.info to debug - #387

Merged
PastaPastaPasta merged 1 commit into
stagingfrom
chore/log-levels
Sep 8, 2026
Merged

chore(logging): demote every logger.info to debug#387
PastaPastaPasta merged 1 commit into
stagingfrom
chore/log-levels

Conversation

@PastaPastaPasta

Copy link
Copy Markdown
Owner

Summary

  • Every logger.info call in app/, components/, hooks/, lib/ and contexts/ becomes logger.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.
  • The logger's production minimum level is info, so until now every one of these printed to the user's browser console. Development builds (min level debug) still show them; NEXT_PUBLIC_LOG_LEVEL=debug shows them anywhere.
  • lib/logger.ts now documents what each level is for so the next call lands at the right one. warn and error are untouched.

Mechanical: one sed-style replace, no argument or message changes. Nothing in e2e/ 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 build all green locally
  • CI
  • Manual: production build console is quiet on the feed; NEXT_PUBLIC_LOG_LEVEL=debug brings the tracing back

🤖 Generated with Claude Code

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.
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying yappr-v2 with  Cloudflare Pages  Cloudflare Pages

Latest commit: 521c431
Status:⚡️  Build in progress...

View logs

@coderabbitai

coderabbitai Bot commented Sep 8, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 2f7d4084-be83-4f43-99b1-24d5ce2e1926

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@PastaPastaPasta
PastaPastaPasta merged commit 0f48a89 into staging Sep 8, 2026
8 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant