fix(logger): handle illegal null/undefined as extra args

[dreamorosi]

Summary

Changes

Please provide a summary of what's being changed

This PR adds an extra runtime check to values passed as extra arguments to a Logger logging method (i.e. logger.info('message', extra);). With the fix added to this PR we are now skipping these values when they are null or undefined rather than trying to process them, which addresses the bug described in the linked issue.

For the sake of completeness, TypeScript already forbids passing these types to the logger methods, so this case could happen only if:

• customers are using JavaScript with no type hints in their IDE
• customers are passing a value of type any
• customers are explicitly turning off type checking for the file / line (i.e. // @ts-expect-error or // @ts-ignore)
• customers are manually type casting the value to make TS happy

Nevertheless, given the above it's still worth adding a runtime check in this case - especially because this case was handled gracefully in previous versions of Logger.

Please add the issue number below, if no issue is present the PR might get blocked and not be reviewed

Issue number: fixes #3613

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud