fix: bugsnag error for emarsys track call #3428
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shrouti1507
requested review from
aashishmalik and
anantjain45823
and removed request for
a team
|
Test report for this run is available at: https://test-integrations-dev.s3.amazonaws.com/integrations-test-reports/rudder-transformer/3428/test-report.html |
ItsSudip
approved these changes
May 30, 2024
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## hotfix-release/v1.68.1 #3428 +/- ##
=======================================================
Coverage 88.01% 88.01%
=======================================================
Files 569 569
Lines 30636 30636
Branches 7325 7327 +2
=======================================================
Hits 26963 26963
- Misses 3338 3366 +28
+ Partials 335 307 -28 ☔ View full report in Codecov by Sentry. |
|
anantjain45823
approved these changes
May 30, 2024
krishna2020
reviewed
May 30, 2024
anantjain45823
added a commit
that referenced
this pull request
May 30, 2024
* fix: tiktok_v2 assigning value to undefined properties (#3426) * fix: tiktok_v2 assigning value to undefined properties * chore: address comments * chore(release): 1.68.1 * fix: bugsnag error for emarsys track call (#3428) --------- Co-authored-by: Anant Jain <[email protected]> Co-authored-by: GitHub Actions <[email protected]> Co-authored-by: shrouti1507 <[email protected]>
anantjain45823
added a commit
that referenced
this pull request
May 30, 2024
chore(release): pull hotfix-release/v1.68.1 into main (#3427) * fix: tiktok_v2 assigning value to undefined properties (#3426) * fix: tiktok_v2 assigning value to undefined properties * chore: address comments * chore(release): 1.68.1 * fix: bugsnag error for emarsys track call (#3428) --------- Co-authored-by: Anant Jain <[email protected]> Co-authored-by: GitHub Actions <[email protected]> Co-authored-by: shrouti1507 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are the changes introduced in this PR?
Adding validation for eventsMapping config. If it is not at all configured, it is not coming as array
What is the related Linear task?
Resolves INT-2204
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?
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.