[CP Staging] Revert "refactor: isolate dismissDuplicateTransactionViolation from Onyx.connect data"#74330
Conversation
…nyx.connect data"
|
@stitesExpensify Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button] |
|
LGTM 👍 Thank you for your hard work! |
Codecov Report❌ Patch coverage is
... and 16 files with indirect coverage changes 🚀 New features to boost your workflow:
|
|
Straight revert, merging without checklists |
|
@luacmartins looks like this was merged without a test passing. Please add a note explaining why this was done and remove the |
…tor/useonyx-deprecate-onyx-connect/dismissDuplicateTransactionViolation-src-libs-actions-Transaction.ts [CP Staging] Revert "refactor: isolate dismissDuplicateTransactionViolation from Onyx.connect data" (cherry picked from commit dfecdfd) (cherry-picked to staging by luacmartins)
|
🚀 Cherry-picked to staging by https://github.com/luacmartins in version: 9.2.44-3 🚀
|
|
Requested a retest here |
|
This revert resolved the linked issue, I checked both off the checklist |
|
🚀 Deployed to production by https://github.com/luacmartins in version: 9.2.44-5 🚀
|
|
🚀 Cherry-picked to staging by https://github.com/luacmartins in version: 9.2.45-0 🚀
|
|
🚀 Deployed to production by https://github.com/luacmartins in version: 9.2.45-6 🚀
|
Reverts #72955
Fixed issues
$ #74255
This PR needs reverted because it lead to a deploy blocker.
The original collection for the violations is here and it was extracting
transaction_from the key in the collection. SoallTransactionViolationwas only keyed by the transactionID.In the new code here, the collection is keyed by
transaction_<transactionID>.This causes the lookups here to fail.
cc @Skalakid