Conversation
|
@eVoloshchak 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] |
Codecov Report✅ Changes either increased or maintained existing code coverage, great job!
|
This comment was marked as outdated.
This comment was marked as outdated.
|
@arosiclair looks like this was merged without a test passing. Please add a note explaining why this was done and remove the |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6c309dc047
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| reportID: item.reportID, | ||
| policyID: item.report?.policyID, | ||
| amount: hasValidModifiedAmount(item) ? Number(item.modifiedAmount) : item.amount, | ||
| amount: item.modifiedAmount ?? item.amount, |
There was a problem hiding this comment.
Fall back to original amount when modifiedAmount is 0
Using item.modifiedAmount ?? item.amount treats an explicitly set modifiedAmount of 0 as valid, but the rest of the app uses 0 as the “unset/missing” sentinel (e.g., other views use modifiedAmount || amount). When a transaction has a real non‑zero amount and modifiedAmount is stored as 0 (common for unmodified transactions), this selection entry will carry amount = 0, which then flows into selected report totals and bulk actions/export. The bug appears whenever modifiedAmount is explicitly 0, causing totals for selected items to be wrong.
Useful? React with 👍 / 👎.
|
straight revert |
[CP Staging] Revert 79085 & 77238 (cherry picked from commit d09fa19) (cherry-picked to staging by arosiclair)
|
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
|
🚀 Cherry-picked to staging by https://github.com/arosiclair in version: 9.2.96-2 🚀
|
|
🚀 Deployed to production by https://github.com/arosiclair in version: 9.2.96-6 🚀
|
|
🚀 Deployed to production by https://github.com/arosiclair in version: 9.2.96-6 🚀
|
|
🚀 Deployed to production by https://github.com/arosiclair in version: 9.2.96-6 🚀
|
|
🚀 Cherry-picked to staging by https://github.com/arosiclair in version: 9.2.97-0 🚀
|
|
🚀 Cherry-picked to staging by https://github.com/arosiclair in version: 9.2.99-0 🚀
|
|
🚀 Deployed to production by https://github.com/francoisl in version: 9.2.99-8 🚀
|
Explanation of Change
Reverts #79085 and #77238
Fixed Issues
$ #79124
$ #79125
$ #79126
$ #79127