Refactor: Remove console.log pollution and implement environment-aware LoggerService#81
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (7)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Description
Replaced hardcoded
console.logstatements across the application's most heavily used components and services with an environment-awareLoggerService. This prevents sensitive PII data and debugging noise from leaking into the production environment console, while maintaining visibility for local development.Related to PSMRI/AMRIT#129
Changes Made
LoggerServicethat checksenvironment.productionflag.LoggerServiceinAppModule.LoggerServiceand replacedconsole.logwiththis.logger.debugin:surveyor-calltype-reports.component.tsbeneficiary-registration-104.component.tscase-sheet.component.tscaseSheet.service.tssearch.service.tsMigration Strategy
This is part 1 of a systematic cleanup of debugging output. Moving to a unified
LoggerServicehelps prepare the application for Angular 19 migration where strict mode and production optimizations will be enforced.