-
Notifications
You must be signed in to change notification settings - Fork 6
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: do not commit User and Client upserts if nothing has changed and fix empty contacts [WPB-15055] #3202
base: release/candidate
Are you sure you want to change the base?
Conversation
…B-15055] (#3188) * fix: do not commit User and Client upserts if nothing has changed [WPB-15055] * fix unused parameter * fix detekt
Quality Gate passedIssues Measures |
I tried multiple different accounts and I couldn't reproduce that on my side: But I believe comparing nullable using @MohamadJaara could you please verify this using the account on which it happened to you? |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release/candidate #3202 +/- ##
=====================================================
+ Coverage 54.14% 54.16% +0.02%
=====================================================
Files 1250 1250
Lines 36477 36495 +18
Branches 3696 3704 +8
=====================================================
+ Hits 19749 19767 +18
+ Misses 15299 15297 -2
- Partials 1429 1431 +2
... and 2 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Datadog ReportBranch report: ✅ 0 Failed, 3241 Passed, 107 Skipped, 1m 1.88s Total Time |
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764
The PR Description
What's new in this PR?
This PR contains cherry-picked changes that were first merged #3188 and then reverted #3198 because contacts data were not persisted properly. Here these changes are brought back along with a fix to persist these data properly. The problem was that in the upsert query, fields were compared using
!=
but some of them are nullable, that's why if the value was set to be null initially and then there was an upsert attempt with proper data,NULL != 'some string'
equalsNULL
instead of boolean value true/false so it never returns a proper result and when working with nullables,IS NOT
should be used instead, so in this PR it's changed to useIS NOT
.Testing
Test Coverage (Optional)
PR Post Submission Checklist for internal contributors (Optional)
PR Post Merge Checklist for internal contributors
References
feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764
.