You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2024-08-01] [$250] Subscription size - Decimal point can be inserted and not removed on the confirmation page #43796
Version Number: 1.4.84-0 Reproducible in staging?: Y Reproducible in production?: Y If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Issue reported by: Applause - Internal Team
@miljakljajic FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
changed the title [-] Subscription size - Decimal point can be inserted and not removed on the confirmation page[/-][+][$250] Subscription size - Decimal point can be inserted and not removed on the confirmation page[/+]on Jun 19, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.11-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@fedirjh] The PR that introduced the bug has been identified. Link to the PR:
[@fedirjh] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[@fedirjh] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[@fedirjh] Determine if we should create a regression test for this bug.
[@fedirjh] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[@miljakljajic] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
Activity
melvin-bot commentedon Jun 15, 2024
Triggered auto assignment to @miljakljajic (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.lanitochka17 commentedon Jun 15, 2024
@miljakljajic FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
Krishna2323 commentedon Jun 15, 2024
Proposal
Please re-state the problem that we are trying to solve in this issue.
Subscription size - Decimal point can be inserted and not removed on the confirmation page
What is the root cause of that problem?
We haven't added a check for decimal point.
App/src/libs/ValidationUtils.ts
Lines 485 to 488 in 75c104b
What changes do you think we should make in order to solve the problem?
Check if the number contains
..What alternative solutions did you explore? (Optional)
We can use
NUMBERregex.What alternative solutions did you explore? (Optional 2)
If we don't want to show error when entering 0 after decimal then we need to trim the decimal points on confirmation page.
App/src/pages/settings/Subscription/SubscriptionSize/substeps/Confirmation.tsx
Line 44 in 75c104b
Additionally we should also clear the draft value when saving the subscription size.
App/src/pages/settings/Subscription/SubscriptionSize/index.tsx
Lines 29 to 32 in 75c104b
To:
Krishna2323 commentedon Jun 15, 2024
Proposal Updated
melvin-bot commentedon Jun 18, 2024
@miljakljajic Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
[-] Subscription size - Decimal point can be inserted and not removed on the confirmation page[/-][+][$250] Subscription size - Decimal point can be inserted and not removed on the confirmation page[/+]melvin-bot commentedon Jun 19, 2024
Job added to Upwork: https://www.upwork.com/jobs/~01d8c409a169a06c82
melvin-bot commentedon Jun 19, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh (
External)21 remaining items
melvin-bot commentedon Jul 25, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.11-5 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 2024-08-01. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jul 25, 2024
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
miljakljajic commentedon Aug 1, 2024
@Krishna2323 you've been paid in upwork, thank you!
@fedirjh your original offer expired as you didn't accept it in upwork in time. Please accept the new offer.
miljakljajic commentedon Aug 1, 2024
actually @fedirjh do we pay you in NewDot? I noticed you're listed for manual payments. Let me know and I'll provide a payment summary instead.
fedirjh commentedon Aug 2, 2024
@miljakljajic Yes, that’s correct. Can you provide a summary instead? Thank you
fedirjh commentedon Aug 2, 2024
BugZero Checklist:
miljakljajic commentedon Aug 5, 2024
Of course, apologies.
@fedirjh is owed 250 for their work reviewing this issue.
JmillsExpensify commentedon Aug 5, 2024
$250 approved for @fedirjh