Remove sensitive console logs that expose user data (Issue #273)#320
Open
anshul23102 wants to merge 2 commits into
Open
Remove sensitive console logs that expose user data (Issue #273)#320anshul23102 wants to merge 2 commits into
anshul23102 wants to merge 2 commits into
Conversation
Removes all console.log, console.warn, and console.error statements that could expose sensitive user information or internal system details. Removed logs that expose: - User streak and points data - User authentication status - Firebase configuration warnings - GitHub authentication errors - Error stack traces with system details - Login/logout activity patterns Prevents data exposure through: - Browser DevTools in development - Analytics and error tracking services - CSP violations and security headers - Third-party monitoring tools Keeps error handling intact by silently catching non-critical errors and properly throwing user-friendly errors for important operations. Fixes issue indresh404#273
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
backend
Contributor
Author
|
Please add relevant labels:
These help with tracking and prioritization. Thank you! |
After removing the sensitive console logs, several catch blocks were left either rethrowing without any added behavior or binding an error variable that is no longer referenced, which failed the eslint check (no-useless-catch) and raised no-unused-vars warnings. Removed the redundant try/catch wrapper in signOutUser so signOut errors propagate directly, and switched the remaining log-free catch blocks to optional catch binding. The onSnapshot error callback argument is renamed to _error to match the allowed unused-argument pattern. eslint now reports zero errors and zero warnings, and the build passes.
Contributor
Author
|
Resolved the failing Lint Check. After removing the sensitive console logs, |
Contributor
Author
Suggested LabelsFor maintainer review and categorization:
Removes sensitive console logs that expose user data and personal information. |
Owner
|
fix conflict |
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
2 participants
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
Removes all console.log, console.warn, and console.error statements that expose sensitive user data and internal system details.
Problem
Console logs expose sensitive information during app operations:
Information exposure through:
Solution
Removed all console statements that log sensitive data:
Silent error handling:
Changes
Modified Files:
Logs Removed:
Security Benefits
Prevents Data Exposure:
Reduces Attack Surface:
Testing Strategy
Files Modified
Fixes #273