-
Notifications
You must be signed in to change notification settings - Fork 5
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
Chore/9630-UseDesignSystemSnackbarComponent #10298
base: develop
Are you sure you want to change the base?
Conversation
@oddballdave please make sure to not merge until QA has tested and approved. This is a large change, so it will take some time. |
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 great for the most part. We'll consider updating the component library to use the patch you created.
Reiterating what we discussed on the call, for Snackbars that need to appear on screens using templates without the nav bar showing such as <FullScreenSubtask />
or <LargePanel />
, if a Snackbar is shown and the user isn't immediately navigated back to a screen that has the nav bar showing, the offset
option should be included with snackbar.show()
to account for the lack of nav bar. This probably would occur mostly with error message Snackbars. You can use theme.dimensions.snackBarBottomOffset
as the offset which automatically calculates the correct offset based on OS.
i.e.
snackbar.show(t('secureMessaging.startNewMessage.sent.error')'), { offset: theme.dimensions.snackBarBottomOffset })
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.
Approving for my part (still needs app team approval) based on the changes.
Moved back to draft until this DS library PR can be incorporated. |
…ffairs/va-mobile-app into chore/9630-UseDesignSystemSnackbarComponent
}, | ||
onError: () => showSnackBar('Request could not be sent', dispatch, () => onSubmit, false, true), | ||
onError: () => | ||
snackbar.show('Request could not be sent', { |
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.
Should we localize 'Request could not be sent'? I see all the other snackbar messages are using localized strings.
@@ -102,9 +102,14 @@ function AskForClaimDecision({ navigation, route }: AskForClaimDecisionProps) { | |||
const mutateOptions = { | |||
onSuccess: () => { | |||
setSubmittedDecision(true) | |||
showSnackBar('Request sent', dispatch, undefined, true, false, true) | |||
snackbar.show('Request sent') |
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.
Same as the comment below
Description of Change
Screenshots/Video
Android (Before)
Android (After)
iOS (Before)
iOS (After)
Testing
Reviewer Validations
PR Checklist
Reviewer: Confirm the items below as you review
For QA
Run a build for this branch