-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Replace growl errors by modal in VBA flow #4924
Conversation
Split setErrorModalVisible into two methods.
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.
Good start. I left a few ideas for improvements.
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.
Changes look perfect! 🏆
I think the one thing left to resolve is that there are some places where the confirm modal title does not entirely make sense. Trying to get a reply to the thread here now
To handle this, would it be fine to include an extra parameter on the
Use it in the display modal like:
Then, when we set the error from the server and want a custom title, we do:
|
Let's wait for feedback first? I haven't seen much discussion about whether these particular errors should have custom titles. |
Hey @marcaaron, considering we are going to use the Oops header, does the proposed way of handling it above work for you? |
Ah no, I think we should make all the headers say "Oops" if that's acceptable? |
Okk, I think I was miss-understanding that we wanted different headers. I will change the generic header of the error modal to "Oops" then! |
Update:
|
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.
Looks perfect there are just two small issues where unnecessary new lines are added. But other than than great work.
Update: removed empty lines |
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.
Looks good! Thanks for the changes!
Approving the code. But we still need to clean up the PR description because there is nothing listed for QA Steps. We need to put something there so that QA knows what to test (and also figure out what QA is able to test or not). Otherwise, they will inevitably ping you (or me since I reviewed) and come asking if there is QA to do or not :)
Also, we should test this on all platforms to make sure the changes are safe. There's checkboxes listed so that we test on every platform. But if there's a good reason not to then we can mention it somewhere.
Oh and also update any screenshots since they are now out of date I think. |
Flo is likely offline for the night. Anyone else we can request? @marcaaron |
@MitchExpensify the comments are for @aldo-expensify 😄 |
I'll start cleaning this up now (QA steps, outdated pictures), thanks for the reminder! |
Updated the Tests section and merged it with QA into There is one thing in the In the Screen.Recording.2021-09-01.at.5.13.40.PM.mov |
Nice! That was just called out by @JmillsExpensify here. I think we'll need to create a follow up issue to look into it. If anything else pops up that you notice we can check in the free plan channel to see if @MitchExpensify & @kevinksullivan are aware of the issue yet. |
Nice one @aldo-expensify! I'll create a follow up issue to change the error copy we use when the age entered is under our required 18 years old |
🚀 Deployed to staging by @marcaaron in version: 1.0.91-2 🚀
|
🚀 Deployed to production by @roryabraham in version: 1.0.92-0 🚀
|
Replacing all growls in the VBA flow by the modal.
The error message coming from the backend is being shown in the ConfirmModal now.
Errors messages associated with inputs where we don't handle highlighting yet, like checkboxes, are shown in the ConfirmModal.
Error modal generic message: 'Please double check any highlighted field and try again'
Fixed Issues
$ #4785
Tests / QA Steps
Company Step: /bank-account/company
/bank-account/company
123123
) and input an invalid phone number (i.e.123
).ACH Contract / Beneficial Owners Step: /bank-account/contract
/bank-account/contract
I accept the terms and conditions
andI certify that the information provided is true and accurate
Somebody else owns more than 25% of XXX
, this will add a form to input a beneficial owner's information. Don't fill any of the beneficial owner data.Requestor Step: /bank-account/requestor
/bank-account/requestor
asd
2020-10-10
Tested On
Screenshots
Web
Mobile Web
Desktop
iOS
Android