-
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
Add confirmation page #13744
Add confirmation page #13744
Conversation
I found a bug (not related to the PR) on pressing cross at confirmation screen of transfer balance page it navigates to the payments pages instead of closing the modal |
@tgolen @sobitneupane One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button] |
Thanks @Puneet-here. Changes are looking good. Will review it today. |
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.
LGTM and tests well!
@shawnborton Tagging you here for a review because I am jsut a bit concerneed about the background colour on some of the gifs. For example look at this: I am not sure if it was raised in other places, but I could not see it in the comments. The Hex of the gif green bg does not seem exactly the same as the app background. You can also check the screenshots in the PR body from Puneet and you can see the colour different there too. Since the images are hosted in cloud we can update that without touching this PR. so I think it is NAB, but wanted to note this |
Good catch. I think we might have to live with this until we replace these GIFs with Lottie animations, where we will have perfectly crisp SVG animations and no background color. |
That being said, I'll flag this to Augenblick and see if they have any ideas! |
Great, thanks, wanted to get a confirmation this is not a blocker 🙇 |
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.
Screenshots/Videos
Web
Web_Enable_Payment.mov
Web_TransferBalance_Confirmation.mov
Web_Company_Information.mov
Web_Change_Password_Confirmation.mov
Web_Request_Call_Confirmation.mov
Web_AddPayment_Confirmation.mov
Web_Enable_Payment_Confirmatioin.mov
Mobile Web - Chrome
Chrome_Company_Information.mov
Chrome_AddPayment_Confirmation.mov
Chrome_Change_Password.mov
Chrom_Request_Call.mov
Chrome_TransferBalance_confirmation.mov
Mobile Web - Safari
Safari_ChangePassword.mov
Safari_RequestCall.mov
Desktop
Desktop_Company_Information.mov
Desktop_AddPayment_Confirmation.mov
Desktop_Change_Password_Confirmation.mov
Desktop_Request_Call_Confirmation.mov
iOS
IOS_Company_information.mov
IOS_Change_Password.mov
IOS_RequestCall.mov
IOS_Add_payment_method.mov
Android
Android_Add_payment_method.mov
Android_Company_information.mov
Android_Change_password.mov
Android_Requestcall.mov
Nice, these look great 🎆 |
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.
@Puneet-here One minor thing
Okay we have two new gifs we can try to fix the BG issue that @mountiny spotted, @Puneet-here can you test with these locally and show us some screenshots? If these look better, I will upload to Cloudfront. |
@shawnborton, it still doesn't match completely with the background Screen.Recording.2022-12-23.at.2.22.13.AM.mov |
Okay no worries, appreciate you giving that a shot! I say we just keep what we have for now and we'll revisit these with Lottie down the road. |
Thank you for updating that, I see this is not super enforced 🙇 We are missing a checklist from @sobitneupane :/ |
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.
Reviewer Checklist
- I have verified the author checklist is complete (all boxes are checked off).
- I verified the correct issue is linked in the
### Fixed Issues
section above - I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the
Tests
section - I verified the steps for Staging and/or Production testing are in the
QA steps
section - I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
- I verified the steps for local testing are in the
- I checked that screenshots or videos are included for tests on all platforms
- I included screenshots or videos for tests on all platforms
- I verified tests pass on all platforms & I tested again on:
- Android / native
- Android / Chrome
- iOS / native
- iOS / Safari
- MacOS / Chrome / Safari
- MacOS / Desktop
- If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
- I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e.
toggleReport
and notonIconClick
). - I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to
src/languages/*
files and using the translation method - I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is correct English and approved by marketing by adding the
Waiting for Copy
label for a copy review on the original GH to get the correct copy. - I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in
STYLE.md
) were followed
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e.
- If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
- I verified that this PR follows the guidelines as stated in the Review Guidelines
- I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like
Avatar
, I verified the components usingAvatar
have been tested & I retested again) - I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
- I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
- If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a
/** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor) - Any internal methods bound to
this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
) - All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
- If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
- If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e.
StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG
)
- If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like
Avatar
is modified, I verified thatAvatar
is working as expected in all cases) - If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
- If a new page is added, I verified it's using the
ScrollView
component to make it scrollable when more elements are added to the page. - I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.
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.
Thank you guys @Puneet-here @sobitneupane 🙇
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
Performance Comparison Report 📊Significant Changes To DurationThere are no entries Meaningless Changes To DurationShow entries
Show details
|
@mountiny @shawnborton Can you pls validate the following steps internally? We do not have active wallet to be able to transfer. Rest steps we are QA-ing
|
🚀 Deployed to production by @chiragsalian in version: 1.2.44-0 🚀
|
Seems this PR caused a regression, i.e missed catching this bug where the welcome text is not centered in Spanish! |
Thanks @Santhosh-Sellavel for linking the issue. Though the bug precedes this PR and was existent in some confirmation screens like |
Details
Fixed Issues
$ #13151
PROPOSAL: #13151 (comment)
Tests
App/src/pages/settings/Payments/TransferBalancePage.js
Line 155 in 3ecec61
App/src/pages/EnablePayments/ActivateStep.js
Line 39 in 3ecec61
Note: At ios you will see that the header is near the status bar. It is because in ActivateStep the ScreenWrapper isn't present as the parent because the parent component of ActivateStep already contains a ScreenWrapper.
Offline tests
No offline specific steps
QA Steps
PR Author Checklist
### Fixed Issues
section aboveTests
sectionOffline steps
sectionQA steps
sectiontoggleReport
and notonIconClick
)src/languages/*
files and using the translation methodWaiting for Copy
label for a copy review on the original GH to get the correct copy.STYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)/** comment above it */
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor)this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)ScrollView
component to make it scrollable when more elements are added to the page.Screenshots/Videos
Web
Screen.Recording.2022-12-22.at.2.03.33.AM.mov
Screen.Recording.2022-12-22.at.3.14.04.AM.mov
Mobile Web - Chrome
Mobile Web - Safari
Desktop
iOS
Android