-
Notifications
You must be signed in to change notification settings - Fork 3.7k
fix(translation): show correct error message for bank account flow #58764
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
Merged
justinpersaud
merged 5 commits into
Expensify:main
from
jaydamani:translation/show-too-many-attempts-error-for-bank-account-flow--57423
Apr 1, 2025
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
dba1693
fix(translation): show correct error message for bank account flow
jaydamani 1fbdf84
prettier
jaydamani fda176f
make max attempt error non dismissable
jaydamani ea2a6f2
Merge branch 'main' into translation/show-too-many-attempts-error-for…
jaydamani 67531a8
add margin for error message
jaydamani File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@Expensify/design what do you think about this change? This is making the error persistent and not allowing you to dismiss it. I'd argue that you can dismiss the error after you've seen it, then that is on you because you saw it and dismissed it. The error will still be presented when they try to setup the bank account again on a different screen.
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.
Hmm I don't feel too strongly. Normally we allow users to dismiss the error, although in this case, if you dismiss the error, the buttons would still be disabled which might feel weird right?
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.
So I think I would keep it there as not dismissable. What makes it so that you can log in again though?
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.
This is for adding a bank account. So in this case, we're showing an error because they've already failed too many times to add a bank account, and their next step is to reach out to Concierge.
If they dismiss the error, they can go through the flow again but then they'll hit the same error page. I think in that case, making it non dismissable is fine since the outcome is the same, right?