-
Notifications
You must be signed in to change notification settings - Fork 114
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: braze dedup for non-billable attributes #3320
Conversation
@coderabbitai review |
Test report for this run is available at: https://test-integrations-dev.s3.amazonaws.com/integrations-test-reports/rudder-transformer/3320/test-report.html |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #3320 +/- ##
========================================
Coverage 87.86% 87.86%
========================================
Files 556 558 +2
Lines 29996 30044 +48
Branches 7172 7191 +19
========================================
+ Hits 26356 26399 +43
- Misses 3336 3342 +6
+ Partials 304 303 -1 ☔ View full report in Codecov by Sentry. |
Quality Gate passedIssues Measures |
What are the changes introduced in this PR?
Fixes for dedup utility for allowing non-billable attributes, previously if only non-billable attributes were only available in traits those were filtered. Now these are allowed
What is the related Linear task?
Resolves INT-2071
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.