-
Notifications
You must be signed in to change notification settings - Fork 59
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
Create UI: Amalgamating Businesses component - Part 3b (remaining validations) #18971
Comments
@yuisotozaki This is the new ticket I'm working on. As part of this ticket:
|
I have to pass the snackbar by the design team. I know we use them but accessibility support isn't good. We don't want to introduce widgets that we'll need to undo later. |
I'm open to alternate designs for add error messaging. Yes, we use the spinner in multiple UI/filings when we need to fetch additional data from the API. << a good example of this is clicking "View Documents" for any ledger items -- it goes and fetches the documents list and any comments the first time you click on this item |
@riyazuddinsyed This ticket is tagged to multiple releases because it has content in several releases (due to multiple, incremental PRs). |
This is ready for UX Assurance. Sample amalgamation applications (try as BCREG0020 and staff): Yui, if you don't like the spinner or the snackbar, please create a new ticket. Thx. For a detailed look at the implemented validation rules, see this code: |
This will be done in #18788. |
Ready for QA. |
This is the second part of ticket #18640. That ticket's estimate of 8 has been reduced to 5, and this ticket is estimated as 3.
Google doc: https://docs.google.com/document/d/1Dt2jzPA2SLtQO7Ns2aPCzVchGdv4YrYB/edit
The text was updated successfully, but these errors were encountered: