test: Add test to ensure null setting strings are handled properly

[alexs-mparticle]

Instructions

1. PR target branch should be against development
2. PR title name should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-title-check.yml
3. PR branch prefix should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-branch-check-name.yml

Summary

• Add test to ensure null setting strings are handled properly

Testing Plan

• Was this tested locally? If not, explain why.
• Using a sample app, ensure Placement Attribute Mapping is being returned as null in the kit config for the Rokt Partner Kit.
• Ensure that verbose logging is on.
• Ensure that no error is being thrown when setting is null.

Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)

• Closes https://go.mparticle.com/work/SDKE-133

[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

[Copilot]

Pull Request Overview

This PR adds a test case to verify that the parseSettingsString function correctly handles null input values by returning an empty array, ensuring robust handling of null setting strings in the codebase.

• Added a unit test to validate null input handling for parseSettingsString

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[mparticle-automation]

🎉 This PR is included in version 2.45.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀