-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Disable letters in Rate under Track Distance #7931
Disable letters in Rate under Track Distance #7931
Conversation
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.
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.
I will continue my review when all the required checklist items are done and STYLING.md is followed. Thanks.
Please add screenshots /videos of al platforms and tick the box |
I am not able to reproduce the issue on staging. Could you please test it @kakajann on prod or staging? |
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.
Thanks for the changes.
Co-authored-by: Rajat Parashar <parasharrajat@users.noreply.github.com>
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.
It looks good. The only thing that I noticed is that user can enter 10.000.00.000
which include multiple decimals.
So this should pick up invalid extra decimals |
Yup, I think so Just don't update the state. That should work. Right? |
That's good idea. I'll update the code tomorrow |
@@ -116,6 +102,32 @@ class WorkspaceReimburseNoVBAView extends React.Component { | |||
}, null); | |||
} | |||
|
|||
handleKeyPress = (event) => { |
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.
No inline functions. Function names should reflect what they do instead of where they are used.
handleKeyPress = (event) => { | |
debounceUpdateOnCursorMove(event) { |
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.
Done
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.
Sorry, I don't see this change. Did you push it?
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.
Whoops, sorry, just a sec
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.
Pushed now
@kakajann Please merge main. Thanks. |
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.
Thanks for the changes looks good.
cc: @pecanoro
PR Reviewer Checklist
- I verified the PR has a small number of commits behind
main
- 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 testing environment is mentioned in the test steps
- I verified testing steps cover success & fail scenarios (if applicable)
- I checked that screenshots or videos are included for tests on all platforms
- I verified tests pass on all platforms & I tested again on:
- iOS / native
- Android / native
- iOS / Safari
- Android / Chrome
- MacOS / Chrome
- MacOS / Desktop
- I verified there are no console errors related to changes in this PR
- I verified proper code patterns were followed (see Reviewing the code)
- I verified comments were added when the code was not self explanatory
- I verified any copy / text shown in the product was added in all
src/languages/*
files (if applicable) - I verified proper naming convention for platform-specific files was followed (if applicable)
- I verified style guidelines were followed
- I verified the JSDocs style guidelines (in
STYLE.md
) were followed
- I verified that this PR follows the guidelines as stated in the Review Guidelines
- I verified other components are not impacted by changes in this PR (i.e. if the PR modifies a shared library or component like
Avatar
, I verified the components usingAvatar
are working as expected) - I verified the UI performance was not affected (the performance is the same than
main
branch) - If a new component is created I verified that a similar component doesn't exist in the codebase
🎀 👀 🎀 C+ reviewed
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to production by @roryabraham in version: 1.1.43-2 🚀
|
👋 @kakajann @parasharrajat @pecanoro - I think this PR has caused a regression that prevents users from entering three decimal places. Can we look into fixing that, please? The default IRS rate is |
Issue for the decimal place rounding down to two instead of three https://github.com/Expensify/Expensify/issues/202283 |
I thought we should round the value down to 2 decimal places. I can make it 3 if it's what has to be done |
Yes please! The IRS rate is 3 decimal places and since we must follow their rules, we need 3 :) |
Details
Keyboard type changed to prevent to type letters in Rate under Track Distance
Fixed Issues
$ #7712
Tests
PR Review Checklist
Contributor (PR Author) Checklist
main
before submitting my PR for review### Fixed Issues
section abovesrc/languages/*
files (if applicable)Styling.md
) for all style edits I madePR Reviewer Checklist
main
before submitting the PR### Fixed Issues
section abovesrc/languages/*
files (if applicable)QA Steps
Tested On
Screenshots
Web
Screen.Recording.2022-02-28.at.11.01.37.AM.mov
Mobile Web
Screen.Recording.2022-03-02.at.2.02.08.PM.mov
Desktop
Screen.Recording.2022-03-02.at.1.58.41.PM.mov
iOS
Screen.Recording.2022-02-28.at.10.57.32.AM.mov
Android
Screen.Recording.2022-02-28.at.11.10.19.AM.mov