-
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: user order #3944
base: develop
Are you sure you want to change the base?
fix: user order #3944
Conversation
fix/moengage-anonymousid-over-userid Co-authored-by: Sudip Paul <[email protected]>
Test report for this run is available at: https://test-integrations-dev.s3.amazonaws.com/integrations-test-reports/rudder-transformer/3944/test-report.html |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #3944 +/- ##
===========================================
+ Coverage 90.48% 90.50% +0.01%
===========================================
Files 615 620 +5
Lines 32359 32518 +159
Branches 7687 7712 +25
===========================================
+ Hits 29281 29429 +148
- Misses 2822 2833 +11
Partials 256 256 ☔ View full report in Codecov by Sentry. |
Quality Gate passedIssues Measures |
Isn't this a breaking change? |
No. We are not sending the userId to destination. We are sending customerId to destination. |
What are the changes introduced in this PR?
We are changing the order of userId and anonymousId.
What is the related Linear task?
Resolves INT-2987
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.