fix: airship array handling

[sanpj2292]

What are the changes introduced in this PR?

"af_arr": [
  "f1",
  "f2",
  {"a":"a1","b":"b2"}
],

// Output
{
  "action": "set",
  "key": "af_arr[0]",
  "value": "f1",
  "timestamp": "2025-01-07T10:57:38Z"
},
{
  "action": "set",
  "key": "af_arr[1]",
  "value": "f2",
  "timestamp": "2025-01-07T10:57:38Z"
},
{
  "action": "set",
  "key": "af_arr[2]_a",
  "value": "a1",
  "timestamp": "2025-01-07T10:57:38Z"
},
{
  "action": "set",
  "key": "af_arr[2]_b",
  "value": "b2",
  "timestamp": "2025-01-07T10:57:38Z"
},

If we send this request to Airship, we are getting a failed response due to presence of [\d] in the request being sent to Airship
Airship destination supports sending JSON attributes while creating/updating attributes. We are trying to make use of this.

For anyone interested in sending JSON attributes, they would need to define JSONAttributes in integrationObject like below:

"integrations": {
  "AIRSHIP": {
    "JSONAttributes": {
      "flights#id123": {
        "recordID": 123,
        "flightsInfo": [
          {
              "departureTime": "2024-07-14T12:35:42+08:00",
              "flightId": "LY205",
              "destinationAirportCode": "PDX",
              "originAirportCode": "LAX"
          },
          {
              "departureTime": "2024-14-14T12:00:00+08:00",
              "flightId": "LY315",
              "destinationAirportCode": "LAX",
              "originAirportCode": "PDX"
          }
        ]
      }
    }
  }
}

We will convert this to below and send it Airship

{
  "action": "set",
  "key": "flights#id123",
  "value": {
        "recordID": 123,
        "flightsInfo": [
          {
              "departureTime": "2024-07-14T12:35:42+08:00",
              "flightId": "LY205",
              "destinationAirportCode": "PDX",
              "originAirportCode": "LAX"
          },
          {
              "departureTime": "2024-14-14T12:00:00+08:00",
              "flightId": "LY315",
              "destinationAirportCode": "LAX",
              "originAirportCode": "PDX"
          }
        ]
   },
  "timestamp": "2025-01-07T10:57:38Z"
},

What is the related Linear task?

Resolves INT-3156

Please explain the objectives of your changes below

Put down any required details on the broader aspect of your changes. If there are any dependent changes, mandatorily mention them here

Any changes to existing capabilities/behaviour, mention the reason & what are the changes ?

N/A

Any new dependencies introduced with this change?

N/A

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

N/A

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

N/A

@coderabbitai review

---

Developer checklist

• My code follows the style guidelines of this project

• No breaking changes are being introduced.

• All related docs linked with the PR?

• All changes manually tested?

• Any documentation changes needed with this change?

• Is the PR limited to 10 file changes?

• Is the PR limited to one linear task?

• Are relevant unit and component test-cases added in new readability format?

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.

[devops-github-rudderstack]

Allure Test reports for this run are available at:

• Allure Report: https://rudderlabs.github.io/rudder-transformer/174/index.html

[codecov]

Codecov Report

Attention: Patch coverage is 97.72727% with 2 lines in your changes missing coverage. Please review.

Project coverage is 91.00%. Comparing base (f7d38d8) to head (d30f055).
Report is 5 commits behind head on develop.

Files with missing lines	Patch %	Lines
src/v0/destinations/airship/utils.ts	97.53%	2 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #4011   +/-   ##
========================================
  Coverage    91.00%   91.00%           
========================================
  Files          630      629    -1     
  Lines        32807    32820   +13     
  Branches      7782     7785    +3     
========================================
+ Hits         29855    29867   +12     
- Misses        2701     2734   +33     
+ Partials       251      219   -32     

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

[devops-github-rudderstack]

Allure Test reports for this run are available at:

• Allure Report: https://rudderlabs.github.io/rudder-transformer/188/index.html

[devops-github-rudderstack]

Allure Test reports for this run are available at:

• Allure Report: https://rudderlabs.github.io/rudder-transformer/190/index.html

[devops-github-rudderstack]

Allure Test reports for this run are available at:

• Allure Report: https://rudderlabs.github.io/rudder-transformer/191/index.html

[devops-github-rudderstack]

Allure Test reports for this run are available at:

• Allure Report: https://rudderlabs.github.io/rudder-transformer/199/index.html

[koladilip]

as discussed add component test cases

[devops-github-rudderstack]

Allure Test reports for this run are available at:

• Allure Report: https://rudderlabs.github.io/rudder-transformer/228/index.html

[devops-github-rudderstack]

Allure Test reports for this run are available at:

• Allure Report: https://rudderlabs.github.io/rudder-transformer/229/index.html

[devops-github-rudderstack]

Allure Test reports for this run are available at:

• Allure Report: https://rudderlabs.github.io/rudder-transformer/274/index.html

[devops-github-rudderstack]

Allure Test reports for this run are available at:

• Allure Report: https://rudderlabs.github.io/rudder-transformer/276/index.html

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud