-
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 [WPB-15055] 🍒 #3195
fix: do not commit User and Client upserts if nothing has changed [WPB-15055] 🍒 #3195
Conversation
…B-15055] (#3188) * fix: do not commit User and Client upserts if nothing has changed [WPB-15055] * fix unused parameter * fix detekt
…-if-nothing-has-changed-cherry-pick
Quality Gate passedIssues Measures |
Test Results2 935 tests - 443 2 926 ✅ - 345 4m 36s ⏱️ -44s Results for commit f2e310d. ± Comparison against base commit 6ddef73. This pull request removes 3378 and adds 2935 tests. Note that renamed tests count towards both.
This pull request removes 107 skipped tests and adds 9 skipped tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
Bencher Report
Click to view all benchmark results
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #3195 +/- ##
========================================
Coverage 54.11% 54.12%
========================================
Files 1264 1264
Lines 36800 36818 +18
Branches 3735 3743 +8
========================================
+ Hits 19915 19927 +12
- Misses 15446 15449 +3
- Partials 1439 1442 +3
... and 4 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
This PR was automatically cherry-picked based on the following PR:
Original PR description:
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764
The PR Description
What's new in this PR?
Issues
When the user data is outdated, the app fetches it again and makes an upsert to the database, but even if there are no changes in the data at all, the insert query is still executed and it notifies all other queries unnecessarily.
Solutions
Make it so that when the app upserts User or Client data and there are absolutely no changes, then rollback that query to not make all other queries that depend on that one dirty.
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
.