fix: error handling when payload contains toString as key

[achettyiitr]

What are the changes introduced in this PR?

• Getting the following error Cannot convert object to primitive value when payload contains toString.
• Resolves PIPE-478
• Sample payload

  [
    {
      "type": "track",
      "properties": {
        "data": {
          "error": {
            "type": "error",
            "extra": {
              "history": {
                "message": "Database transaction failed.",
                "errorDetails": [
                  {
                    "operation": "transaction"
                  },
                  {
                    "code": "ERR_HTTP_HEADERS_SENT",
                    "type": "Error",
                    "stack": "Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client",
                    "message": "Cannot set headers after they are sent to the client",
                    "toString": "[function]"
                  }
                ]
              }
            }
          }
        }
      },
      "receivedAt": "2023-12-21T16:21:53.045Z"
    }
  ]
  

Please explain the objectives of your changes below

Error handling when payload contains toString as key.

Type of change

bug-fix

• Error handling when payload contains toString as key

If the pull request is a new feature,

Any technical or performance-related pointers to consider with the change?

N/A

Any new dependencies introduced with this change?

N/A

Any new generic utility introduced or modified. Please explain the changes.

N/A

If the PR has changed in more than 10 files, please mention why the changes were not split into multiple PRs.

N/A

If multiple linear tasks are associated with the PR changes, please elaborate on the reason:

N/A

---

Developer checklist

• No breaking changes are being introduced.

• Are all related docs linked with the PR?

• Are all changes manually tested?

• Does this change require any documentation changes?

• Are relevant unit and component test-cases added?

Reviewer checklist

• Is the type of change in the PR title appropriate as per the changes?

• Verified that there are no credentials or confidential data exposed with the changes.

[coderabbitai]

Important

Auto Review Skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository.

To trigger a single review, invoke the @coderabbitai review command.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• You can directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• You can tag CodeRabbit on specific lines of code or entire files in the PR by tagging @coderabbitai in a comment. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• You can tag @coderabbitai in a PR comment and ask questions about the PR and the codebase. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid.
  • @coderabbitai read the files in the src/scheduler package and generate README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (66a5390) 87.18% compared to head (c437f1f) 87.19%.
Report is 5 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #2954   +/-   ##
========================================
  Coverage    87.18%   87.19%           
========================================
  Files          860      860           
  Lines        29303    29322   +19     
  Branches      6837     6841    +4     
========================================
+ Hits         25547    25566   +19     
  Misses        3410     3410           
  Partials       346      346           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud