Add unit tests for maskSensitive helper covering nested objects and array values

[Chucks1093]

Summary

The maskSensitive helper has tests for flat objects but no coverage for nested objects or arrays containing objects with sensitive keys. Both cases appear in real log context payloads and need to be handled correctly.

Scope

• Test nested object: { webhook: { url: 'https://example.com' } } → url masked inside the nested object
• Test array of objects: { hooks: [{ callback: 'x' }, { callback: 'y' }] } → both callback values masked
• Test non-sensitive nested key unchanged: { meta: { count: 5 } } → count value preserved
• Test deeply nested sensitive key (3 levels) is masked

Acceptance Criteria

• Sensitive keys in nested objects are masked
• Sensitive keys inside array items are masked
• Non-sensitive nested keys unchanged
• Three-level nesting handled correctly

ETA: 12 hours

---

Coordinate on Telegram

[akinboyewaSamson]

Hi Maintainer,

I would love to be assigned to this issue.

I’m a Full-Stack Developer and I also actively explore blockchain development and smart contracts, which has strengthened my problem-solving skills and attention to code quality.

After reviewing the issue, I believe I can contribute effectively and deliver a well-tested solution within the expected standards of the project.

ETA: 6 hours

Thank you for your consideration.

[Killerjunior]

@Killerjunior has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi maintainer, I have read and understood the issue requirements and checked the necessary documentation. I’m confident I can work on this task effectively and deliver a proper solution.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Killerjunior to this issue.

[Legit003]

@Legit003 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi maintenaner
I would like to work on this issue, please give me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Legit003 to this issue.

[drips-wave]

Congratulations, @Killerjunior! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Killerjunior: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @Killerjunior as part of the Stellar Wave Program's 7th Wave 🥳

😎 @Killerjunior: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.