-
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
[HOLD for payment 2021-09-27] IOU - Modal is shifted to the left when entering a long amount number #5115
Comments
Triggered auto assignment to @bondydaa ( |
Proposed Solution If we know that we're going to have a max value for the amount then we should add a maxLength property to the amount field. I added 14 and it worked fine. Then basically it didn't messed up the alignment of the the button as well.
|
15 digits would be 900 billion max, currently the richest person in the world is Jeff Bezos with an estimated 177 billion and while I do hope we eventually have Mr Bezos using expensify to settle up his IOUs I don't think 15-20 digit numbers are going to be super common use case here so I think I agree we should just add a |
Triggered auto assignment to @stephanieelliott ( |
i don't think this needs to be a daily so once the job is created we could move this to weekly or monthly. |
Maybe countries with high inflations might be affected by this, e.g Venezuela, currently 1$ is equal to 4.200.000 Bs. So having an IOU of 1000$ would be 4.200.000.000 Bs. It still doesn't reach the 14 digit mark so I agree with Bondy that this will not be a common issue. |
Yeah that crossed my mind too but for the time being I believe IOUs can
only be in USD. Though something might have changed there that I might have
missed so if we think it might be more common then maybe style changes are
needed.
…On Tue, Sep 7, 2021 at 11:39 AM Isabella Goicoechea < ***@***.***> wrote:
Maybe countries with high inflations might be affected by this, e.g
Venezuela, currently 1$ is equal to 4.200.000 Bs. So having an IOU of 1000$
would be 4.200.000.000 Bs. It still doesn't reach the 14 digit mark so I
agree with Bondy that this will not be a common issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5115 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7CPCWA6WY7EUESXSY37JTUAZE6NANCNFSM5DRH7AJQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Considering that the issue is uncommon, I suggested the |
Triggered auto assignment to @deetergp ( |
Posted to Upwork here: https://www.upwork.com/jobs/~013d0ec60b16212278 @deetergp looks like we have a proposal in this comment. |
I agree that we can kick the can down the street on 15+ digit numbers for the time being. Let's go with @akshayasalvi proposal of just adding a max length of 14 digits. |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
Hey @akshayasalvi can you please propose to the job post in Upwork so I can hire and pay you for this: https://www.upwork.com/jobs/~013d0ec60b16212278 |
@stephanieelliott Done. Thanks for the help. |
🚀 Deployed to staging by @marcaaron in version: 1.0.97-1 🚀
|
🚀 Deployed to production by @francoisl in version: 1.0.98-1 🚀
|
1 similar comment
🚀 Deployed to production by @francoisl in version: 1.0.98-1 🚀
|
🚀 Deployed to staging by @francoisl in version: 1.0.98-2 🚀
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.0.98-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2021-09-27. 🎊 |
This message is a bug, caused by today's deploy and some weird GH API behaviour. Updated the title back to what it was 🙇 |
@stephanieelliott Is this payment on hold? |
Was there a regression from this PR? If not, it should have been paid on 22nd September. Sorry for confusion because of the bot message 😬 @stephanieelliott |
@stephanieelliott @deetergp Still waiting for this one to get paid out. @mountiny Sorry for tagging you. I thought you were the CME. |
Yikes, apologies @akshayasalvi, we are having a bit busy times so some tasks simply slip from our radar. I will ping someone! |
Thanks for the quick response @mountiny. Any expected date, so that I don't have to ping you :P |
@akshayasalvi I think someone will do it today for sure, I have pinged our team and there will be at least one one person with time to handle this. Sorry for the delay and we appreciate you patience 🙇 |
Scheduling payment now - sorry for the delay @akshayasalvi ! |
Payment sent, job posting closed! |
@dylanexpensify I received half the payment I guess. I reported + resolved the issue. |
Ahh my apologies @akshayasalvi! One second |
Thanks @mountiny. Received help on this. :) |
No problem @dylanexpensify. Sorry if my follow up got you rushing into this |
@akshayasalvi no no, you're all good!! I just sent over the bonus 😄 |
Thank you @dylanexpensify and @mountiny 😄 |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
Modal should stay on the visible area of the screen
Actual Result:
Modal is shifted to the left and button is not completely visible.
Workaround:
N/A
Platform:
Where is this issue confirmed?
Version Number: 1.0.94-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
View all open jobs on GitHub
From @akshayasalvi https://expensify.slack.com/archives/C01GTK53T8Q/p1630779418448200
The text was updated successfully, but these errors were encountered: