Repository navigation
Revert "Restore: Show up to three report fields per row and edit them inline" - #104513
AndrewGable wants to merge 1 commit into
Conversation
|
Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers! |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Codecov Report❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.
|
JmillsExpensify
left a comment
There was a problem hiding this comment.
No product review required
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ce431eaf75
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| if (value !== '') { | ||
| updateReportField({ |
There was a problem hiding this comment.
Persist cleared optional text fields
When a deletable text report field is cleared, EditReportFieldText permits the empty value because the field is not required, but this guard skips updateReportField() and immediately navigates away. The previous value therefore remains stored, so users can replace the value but cannot clear it; allow an empty value for optional text fields while continuing to reject empty report titles.
Useful? React with 👍 / 👎.
| <OfflineWithFeedback | ||
| // Need to return undefined when we have pendingAction to avoid the duplicate pending action | ||
| pendingAction={pendingAction ? undefined : report?.pendingFields?.[reportField.fieldKey as keyof typeof report.pendingFields]} | ||
| errorRowStyles={styles.ph5} | ||
| key={`menuItem-${reportField.fieldKey}`} | ||
| onClose={() => clearReportFieldKeyErrors(report?.reportID, reportField.fieldKey)} |
There was a problem hiding this comment.
Pass field update failures to OfflineWithFeedback
When a report-field update fails on a multi-expense report, updateReportField() rolls back the value and stores the failure in report.errorFields[fieldKey], but this wrapper no longer passes that error to OfflineWithFeedback. The field consequently reverts without displaying the stored failure or a dismiss control; restore the errors prop alongside pendingAction as is still done in MoneyReportView.
Useful? React with 👍 / 👎.
| if (!oldValue) { | ||
| return translate('report.actions.type.changeFieldEmpty', newValue, fieldName); | ||
| } |
There was a problem hiding this comment.
Handle cleared field actions as removals
For an OldDot CHANGE_FIELD action with a populated oldValue and an empty newValue, this now falls through to changeField and renders text such as changed Project to "" (previously "Apollo"). These actions can still arrive from other clients even while this commit prevents the local clear flow, so retain the removed-field branch and translation for accurate report history.
Useful? React with 👍 / 👎.
|
Let's give QA some more time to run additional tests. If there are only 1–2 blockers, I'll go ahead and create a follow-up PR soon |
|
Currently there's only one blocker. Should I create a follow-up PR to fix it instead of reverting our PR? |
|
I would prefer to try if there is just one. |
|
@daledah Could you raise the follow-up PR? |
|
Melvin created a follow up PR here #104551 |
|
@inimaga @JmillsExpensify @AndrewGable Here's the PR: #104551 It currently shows Is that acceptable? If we want Screen.Recording.2026-10-21.at.18.36.28.mov |
|
That looks fine to me. |
|
Closing, CPing the fix #104551 |
Straight revert #104124
Fixes $ #104507