[Performance] Optimize sanitizedHeadersOutput#7635
Conversation
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
WHY are these changes introduced?
The
sanitizedHeadersOutputfunction is called for every network request to format headers for logging. Even when debug logging is disabled, it performs expensive string manipulation and object iteration, which is unnecessary overhead.WHAT is this pull request doing?
!isVerbose() && !isUnitTest()).SENSITIVE_HEADERSto avoid repeated allocations.Object.entriesand a singletoLowerCase()call per header.How to test your changes?
CI
Post-release steps
None.
Checklist
patchfor bug fixes ·minorfor new features ·majorfor breaking changes) and added a changeset withpnpm changeset addPR created automatically by Jules for task 1039541295515390170 started by @gonzaloriestra