-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[Due for payment 2025-04-14] [$250] Ensure we only have one error message show for forms that have only one input #55649
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
Comments
Coming from this internal slack post for visibility for internal members. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Ensure we only have one error message show for forms that have only one input What is the root cause of that problem?Improvement Task What changes do you think we should make in order to solve the problem?
For this, we will review all the usage of
After doing the previous step, we will use pre-existing prop named One example of existing usage -
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?NA since this is an UI change What alternative solutions did you explore? (Optional) |
Added a mock to OP to make it a little more clear what the expected outcome would look like. |
@dylanexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
NICE! Thanks @dannymcclain! |
Job added to Upwork: https://www.upwork.com/jobs/~021885281718152248847 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rojiphil ( |
@rojiphil, @dylanexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Will review today |
@shubham1206agra proposal to use |
Triggered auto assignment to @roryabraham, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Nice! Rory to confirm |
bump le @roryabraham 🙇♂ |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@shubham1206agra mind giving an update? |
Waiting for approval from @roryabraham |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.23-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2025-04-14. 🎊 For reference, here are some details about the assignees on this issue:
|
@roryabraham le bump! |
@dylanexpensify Eep! 4 days overdue now. Issues have feelings too... |
Payment summary: Contributor: @rojiphil $250 via Upwork Please apply/request! |
@shubham1206agra sent new offer! |
@dylanexpensify My payment should be on NewDot. |
Thanks @dylanexpensify for the payment summary. I have requested in ND. |
$250 approved for @shubham1206agra |
$250 approved for @rojiphil |
Uh oh!
There was an error while loading. Please reload this page.
Problem: moving into a newDot world, we've been able to make a lot of our forms shorter and with fewer inputs per form. When users make an input that isn't the correct format for the form an error is thrown both in the input and at the bottom of the form. When they click on the hyperlink to fix the error, it autofocuses them to the input in question. This can result in confusion though for a user when multiple error messages show for a form that has only one input.
Solution: remove footer errors when only one input exists in a form. This removes any confusion for a user who might click on the hyperlink and be brought to the only input.
Next steps:
Mocks

cc @Expensify/design
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @dylanexpensifyThe text was updated successfully, but these errors were encountered: