Skip to content

changed logic to use 2 decimals instead of 3#6499

Merged
TomatoToaster merged 1 commit into
mainfrom
dsilva_changeIOUAmountToTwoDecimals
Nov 29, 2021
Merged

changed logic to use 2 decimals instead of 3#6499
TomatoToaster merged 1 commit into
mainfrom
dsilva_changeIOUAmountToTwoDecimals

Conversation

@danieldoglas

@danieldoglas danieldoglas commented Nov 29, 2021

Copy link
Copy Markdown
Contributor

cc: @rushatgabhane

Details

We were allowing 3 decimal cases in the amount field on Send Money/Request money. Changed it to 2.

Fixed Issues

$ #6286

QA Steps:

  1. Navigate to a conversation
  2. Request money
  3. Verify you cannot enter an amount with 3 decimal places.

@danieldoglas danieldoglas requested a review from a team as a code owner November 29, 2021 16:10
@github-actions

github-actions Bot commented Nov 29, 2021

Copy link
Copy Markdown
Contributor

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@MelvinBot MelvinBot requested review from TomatoToaster and removed request for a team November 29, 2021 16:11
@danieldoglas

Copy link
Copy Markdown
Contributor Author

I have read the CLA Document and I hereby sign the CLA

@TomatoToaster

TomatoToaster commented Nov 29, 2021

Copy link
Copy Markdown
Contributor

LGTM feel free to merge when the E2E tests finish. @danieldoglas Could you also add the reproduction steps from the original issue to this one for the QA steps? I think it's fine to copy and paste it.

@TomatoToaster TomatoToaster merged commit de6aca9 into main Nov 29, 2021
@TomatoToaster TomatoToaster deleted the dsilva_changeIOUAmountToTwoDecimals branch November 29, 2021 21:20
@OSBotify

Copy link
Copy Markdown
Contributor

@danieldoglas, Great job getting your first Expensify/App pull request over the finish line! 🎉

I know there's a lot of information in our contributing guidelines, so here are some points to take note of 📝:

  1. Now that your first PR has been merged, you can be hired for another issue. Once you've completed a few issues, you may be eligible to work on more than one job at a time.
  2. Once your PR is deployed to our staging servers, it will undergo quality assurance (QA) testing. If we find that it doesn't work as expected or causes a regression, you'll be responsible for fixing it. Typically, we would revert this PR and give you another chance to create a similar PR without causing a regression.
  3. Once your PR is deployed to production, we start a 7-day timer ⏰. After it has been on production for 7 days without causing any regressions, then we pay out the Upwork job. 💰

So it might take a while before you're paid for your work, but we typically post multiple new jobs every day, so there's plenty of opportunity. I hope you've had a positive experience contributing to this repo! 😊

@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

OSBotify commented Dec 7, 2021

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by @TomatoToaster in version: 1.1.17-8 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@OSBotify

OSBotify commented Dec 8, 2021

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by @roryabraham in version: 1.1.18-3 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants