fix(278): object sanitization for sensitive keys with non-string values#282
Conversation
|
@copilot use my PR template for the PR summary, do not make up your own |
You’re right—I only acknowledged it and didn’t update the PR body at that point. I’ll apply your template format exactly (Overview, Details, Related Tickets and/or Pull Requests) in the PR summary update next. |
why are you lying to me? you still did not update it do you actually understand what I'm asking you to do? |
... Yes. You’re asking me to update the PR summary itself to your exact template sections: Overview, Details, and Related Tickets and/or Pull Requests. I did not actually make that update yet. |
Overview
Address code review comments raised against the
objectReplacerandsanitizeDatachanges.Details
sanitizeDataJSDoc insrc/index.tsto accurately describe the control flow: strings go throughstringReplacer, non-null objects go directly throughobjectReplacer, andnullis stringified then sanitized viastringReplacer.sanitizeValueinsrc/replacers.tsto preserve non-plain objects (e.g.Date,Map,Set, class instances) instead of silently flattening them to{}. A prototype check now returns such values unchanged.Related Tickets and/or Pull Requests
Relates to #278