Skip to content
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

[$250] Request Money - Inconsistent Padding Between Error Message and Save Button in Tax value section #39922

Closed
1 of 6 tasks
izarutskaya opened this issue Apr 9, 2024 · 20 comments
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. External Added to denote the issue can be worked on by a contributor Monthly KSv2 Reviewing Has a PR in review

Comments

@izarutskaya
Copy link

izarutskaya commented Apr 9, 2024

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!


Version Number: v1.4.61-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers): [email protected]
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

1,Navigate to Profile > Workspace > Create Workspace.
2, Enable tax feature under More Features > Tax Rate 1.
3, Go to the Value section, clear the number, and attempt to save. Observe the padding between the save button and the error message.
4, Access FAB > Request Money > Add Amount > Choose Split With.
5, Proceed to the Tax Amount section and attempt to save without entering anything. Note the padding between the error message and the save button.
6, The padding between the error message and the save button in the Tax Value section and Tax Amount section is inconsistent.

Expected Result:

The padding between the error message and the save button in the Tax Value section should be consistent with other number value sections.

Actual Result:

The padding between the error message and the save button in the Tax Value section increases significantly and is inconsistent with other number value sections.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6443310_1712659066045.Screen_Recording_2024-04-09_at_3.32.38_AM.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01d37ed51248fa5380
  • Upwork Job ID: 1777812961038524416
  • Last Price Increase: 2024-04-09
  • Automatic offers:
    • hungvu193 | Reviewer | 0
    • Krishna2323 | Contributor | 0
@izarutskaya izarutskaya added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Apr 9, 2024
Copy link

melvin-bot bot commented Apr 9, 2024

Triggered auto assignment to @MitchExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

@izarutskaya
Copy link
Author

We think this issue might be related to the #collect project.

@Krishna2323
Copy link
Contributor

Krishna2323 commented Apr 9, 2024

Proposal

Please re-state the problem that we are trying to solve in this issue.

Request Money - Inconsistent Padding Between Error Message and Save Button in Tax value section

What is the root cause of that problem?

We haven't added styles.mt0 to submitButtonStyles in ValuePage.

submitButtonStyles={[styles.mh5]}

What changes do you think we should make in order to solve the problem?

We need to just pass styles.mt0 to submitButtonStyles and it will fix the issue.

We use always pass styles.mt0 when we use AmountForm in other components.

submitButtonStyles={[styles.mh5, styles.mt0]}
disablePressOnEnter={false}
>
<InputWrapperWithRef
InputComponent={AmountForm}

submitButtonStyles={[styles.mh5, styles.mt0]}
disablePressOnEnter={false}
>
<InputWrapperWithRef
InputComponent={AmountForm}

submitButtonStyles={[styles.mh5, styles.mt0]}
disablePressOnEnter={false}
>
<InputWrapperWithRef
InputComponent={AmountForm}

What alternative solutions did you explore? (Optional)

@Krishna2323
Copy link
Contributor

Proposal Updated

  • Added references

@MitchExpensify MitchExpensify added the External Added to denote the issue can be worked on by a contributor label Apr 9, 2024
@melvin-bot melvin-bot bot changed the title Request Money - Inconsistent Padding Between Error Message and Save Button in Tax value section [$250] Request Money - Inconsistent Padding Between Error Message and Save Button in Tax value section Apr 9, 2024
Copy link

melvin-bot bot commented Apr 9, 2024

Job added to Upwork: https://www.upwork.com/jobs/~01d37ed51248fa5380

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Apr 9, 2024
Copy link

melvin-bot bot commented Apr 9, 2024

Triggered auto assignment to Contributor-plus team member for initial proposal review - @hungvu193 (External)

@hungvu193
Copy link
Contributor

hungvu193 commented Apr 10, 2024

@Krishna2323's proposal here is straightforward and looks good to me
🎀 👀 🎀 C+ reviewed

@hungvu193
Copy link
Contributor

🎀 👀 🎀

Copy link

melvin-bot bot commented Apr 10, 2024

Triggered auto assignment to @lakchote, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

@lakchote
Copy link
Contributor

@Krishna2323's proposal LGTM

@melvin-bot melvin-bot bot removed the Help Wanted Apply this label when an issue is open to proposals by contributors label Apr 10, 2024
Copy link

melvin-bot bot commented Apr 10, 2024

📣 @hungvu193 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job

Copy link

melvin-bot bot commented Apr 10, 2024

📣 @Krishna2323 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

@hungvu193
Copy link
Contributor

@Krishna2323 do you have any ETA for the PR?

@Krishna2323
Copy link
Contributor

@hungvu193, PR is ready for video, only the recording for android native is remaining, there are some build issues.

@hungvu193
Copy link
Contributor

hungvu193 commented Apr 11, 2024

@hungvu193, PR is ready for video, only the recording for android native is remaining, there are some build issues.

Cool. That's fine because Android build is failing after new arch was enable, can you check all checklist please?

@Krishna2323
Copy link
Contributor

@hungvu193, done!

@Krishna2323
Copy link
Contributor

@MitchExpensify, PR was deployed to production on 22nd April, this is ready for the payments process.

@MitchExpensify
Copy link
Contributor

Payment summary:

C $250 @Krishna2323
C+ $250 @hungvu193

@melvin-bot melvin-bot bot added Monthly KSv2 and removed Weekly KSv2 labels May 29, 2024
Copy link

melvin-bot bot commented May 29, 2024

This issue has not been updated in over 15 days. @hungvu193, @lakchote, @MitchExpensify, @Krishna2323 eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

@hungvu193
Copy link
Contributor

We're good to close this one ☝️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. External Added to denote the issue can be worked on by a contributor Monthly KSv2 Reviewing Has a PR in review
Projects
No open projects
Archived in project
Development

No branches or pull requests

5 participants