-
Notifications
You must be signed in to change notification settings - Fork 72
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
Ignore 404 - Kustomer and Delighted #4593
Ignore 404 - Kustomer and Delighted #4593
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
d4c1e20
to
43aaadf
Compare
Passing run #6483 ↗︎
Details:
Review all test suite changes for PR #4593 ↗︎ |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4593 +/- ##
=======================================
Coverage 86.67% 86.67%
=======================================
Files 336 336
Lines 20090 20090
Branches 2581 2581
=======================================
Hits 17414 17414
Misses 2203 2203
Partials 473 473 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both of these looks good, just make sure to bump the version number for Delighted and Kustomer so the auto-update takes effect.
…-1646-ignore-404-delighted-kustomer
I don't know how this got so lost, but circling back finally @galvana 😅 |
Closes PROD-1646
Description Of Changes
An edge case found when an erasure for the same user is approved simultaneously, allowing the access portion to succeed (user found) but only one erasure to succeed while the other results in a 404.
As the desired result is to have the user no longer found, ignoring a 404 in this situation feels like the right course of action.
Code Changes
Steps to Confirm
Pre-Merge Checklist
CHANGELOG.md