-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: adding check for reserved key words in extract custom fields #3264
Conversation
Test report for this run is available at: https://test-integrations-dev.s3.amazonaws.com/integrations-test-reports/rudder-transformer/3264/test-report.html |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #3264 +/- ##
===========================================
+ Coverage 87.78% 87.84% +0.06%
===========================================
Files 556 556
Lines 29832 29932 +100
Branches 7110 7146 +36
===========================================
+ Hits 26188 26295 +107
+ Misses 3308 3305 -3
+ Partials 336 332 -4 ☔ View full report in Codecov by Sentry. |
Please consider if this is a breaking change or not. |
dropping the reserved keys as @koladilip suggested here. Added test cases for all |
Quality Gate passedIssues Measures |
What are the changes introduced in this PR?
Solution of bugsnag error
What is the related Linear task?
Resolves INT-1986
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.
Change is
extractCustomField
to solve bugsnag errorAny 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.