docs(rules): add safe examples to javascript_lang_logger_leak#485
Open
vincent067 wants to merge 1 commit into
Open
docs(rules): add safe examples to javascript_lang_logger_leak#485vincent067 wants to merge 1 commit into
vincent067 wants to merge 1 commit into
Conversation
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
1 participant
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.
Hi team! 👋
This small PR adds safe-code examples to the remediation section of the
javascript_lang_logger_leakrule, as suggested in Bearer/bearer#1701.What changed:
info).debuglevels for detailed data, assuming debug is disabled in production.I tried to keep the tone consistent with the existing documentation—hope it helps new users understand the fix at a glance. 😊
Happy to adjust the wording or examples if anything feels off. Just let me know!
Cheers,
Vincent
Closes Bearer/bearer#1701