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

[HOLD for payment 2024-06-20] [HOLD for payment 2024-06-18] [$125] Incorrect padding in group invite flow in RHP #42594

Closed
1 of 6 tasks
m-natarajan opened this issue May 24, 2024 · 32 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 External Added to denote the issue can be worked on by a contributor

Comments

@m-natarajan
Copy link

m-natarajan commented May 24, 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: 1.4.75-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:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @shawnborton
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1716499799827299

Action Performed:

  1. Create a group
  2. Click on the header > members>invite member
  3. Observe the padding surrounding the whole thing and the button at the bottom

Expected Result:

There should not be any padding around RHP content and no extra space below the footer button

Actual Result:

There is a padding around the RHP content and extra space below the footer button

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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

Add any screenshot/video evidence
CleanShot 2024-05-23 at 23 30 17@2x
CleanShot 2024-05-23 at 23 30 43@2x
Screenshot 2024-05-24 094651

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0112cf7031d552a86f
  • Upwork Job ID: 1794119738268631040
  • Last Price Increase: 2024-05-24
  • Automatic offers:
    • GandalfGwaihir | Contributor | 102490661
Issue OwnerCurrent Issue Owner: @mallenexpensify
@m-natarajan m-natarajan added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels May 24, 2024
Copy link

melvin-bot bot commented May 24, 2024

Triggered auto assignment to @mallenexpensify (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.

@dragnoir
Copy link
Contributor

Proposal

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

extra button margin at the bottom

What is the root cause of that problem?

extra margin at

containerStyles={[styles.flexReset, styles.flexGrow0, styles.flexShrink0, styles.flexBasisAuto, styles.mb5]}

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

remove the styles.mb5

containerStyles={[styles.flexReset, styles.flexGrow0, styles.flexShrink0, styles.flexBasisAuto, styles.mb5]}

@ShridharGoel
Copy link
Contributor

Proposal

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

Incorrect padding in group invite flow in RHP.

What is the root cause of that problem?

There is extra padding in View which wraps the SelectionList.

<View style={[styles.flex1, styles.p1]}>

There is extra padding in containerStyles in the FormAlertWithSubmitButton.

containerStyles={[styles.flexReset, styles.flexGrow0, styles.flexShrink0, styles.flexBasisAuto, styles.mb5]}

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

styles.mb5 should be removed:

containerStyles={[styles.flexReset, styles.flexGrow0, styles.flexShrink0, styles.flexBasisAuto]}

styles.p1 should be removed:

<View style={[styles.flex1]}>
    <SelectionList
        canSelectMultiple
        sections={sections}
        ListItem={InviteMemberListItem}
        textInputLabel={translate('selectionList.nameEmailOrPhoneNumber')}
        textInputValue={searchTerm}
        onChangeText={setSearchTerm}
        headerMessage={headerMessage}
        onSelectRow={toggleOption}
        onConfirm={inviteUsers}
        showScrollIndicator
        shouldPreventDefaultFocusOnSelectRow={!DeviceCapabilities.canUseTouchScreen()}
        showLoadingPlaceholder={!didScreenTransitionEnd || !OptionsListUtils.isPersonalDetailsReady(personalDetails)}
    />
</View>

@allgandalf
Copy link
Contributor

Proposal

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

Incorrect bottom and top padding

What is the root cause of that problem?

We have extra padding at ta number of places, we need to update the style at 3 components:

<View style={[styles.flexShrink0, styles.p5]}>

<View style={[styles.flex1, styles.p1]}>

extra margin:
containerStyles={[styles.flexReset, styles.flexGrow0, styles.flexShrink0, styles.flexBasisAuto, styles.mb5]}

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

Update the style to make the top padding as 0:

<View style={[styles.flexShrink0, styles.p5]}>

<View style={[styles.flexShrink0, styles.p5, styles.pt0]}> 

Remove the bottom margin:

containerStyles={[styles.flexReset, styles.flexGrow0, styles.flexShrink0, styles.flexBasisAuto, styles.mb5]}

containerStyles={[styles.flexReset, styles.flexGrow0, styles.flexShrink0, styles.flexBasisAuto]}

remove the extra padding:

<View style={[styles.flex1, styles.p1]}>

<View style={[styles.flex1]}>

The above style changes will be inline with the Workspace invite members page:

Workspace Invite Members Page Updated Group Invite Members Page
Screenshot 2024-05-24 at 10 04 17 PM Screenshot 2024-05-24 at 10 04 30 PM

@mallenexpensify mallenexpensify changed the title Incorrect padding in group invite flow in RHP [$125] Incorrect padding in group invite flow in RHP May 24, 2024
Copy link

melvin-bot bot commented May 24, 2024

⚠️ Could not update price automatically because there is no linked Upwork Job ID. The BZ team member will need to update the price manually in Upwork.

@mallenexpensify mallenexpensify added the External Added to denote the issue can be worked on by a contributor label May 24, 2024
Copy link

melvin-bot bot commented May 24, 2024

Job added to Upwork: https://www.upwork.com/jobs/~0112cf7031d552a86f

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

melvin-bot bot commented May 24, 2024

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

@mallenexpensify
Copy link
Contributor

Looks like this should be super quick/easy so I'm setting the price at $125. @thesahindia , 👀 plz on the above proposals

Copy link

melvin-bot bot commented May 25, 2024

📣 @zdradaa! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

  1. Make sure you've read and understood the contributing guidelines.
  2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
  3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
  4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
    Screen Shot 2022-11-16 at 4 42 54 PM
    Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

Copy link

melvin-bot bot commented May 25, 2024

✅ Contributor details stored successfully. Thank you for contributing to Expensify!

@zdradaa
Copy link

zdradaa commented May 25, 2024

Remove extra space below the footer button and remove padding around the RHP content
image
image

SachinNautiyal-gitHub added a commit to SachinNautiyal-gitHub/App that referenced this issue May 25, 2024
Copy link

melvin-bot bot commented May 25, 2024

📣 @SachinNautiyal-gitHub! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

  1. Make sure you've read and understood the contributing guidelines.
  2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
  3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
  4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
    Screen Shot 2022-11-16 at 4 42 54 PM
    Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

@SachinNautiyal-gitHub
Copy link

Contributor details
Your Expensify account email: [email protected]
Upwork Profile Link: https://www.upwork.com/freelancers/~01b7353984e10e506c

Copy link

melvin-bot bot commented May 25, 2024

✅ Contributor details stored successfully. Thank you for contributing to Expensify!

@SachinNautiyal-gitHub
Copy link

Proposal

Please re-state the problem that we are trying to solve in this issue.
extra padding and margin on top and bottom

What is the root cause of that problem?

extra padding at number of places

Root cause of issue - Extra margin in "App/src/pages/InviteReportParticipantsPage.tsx" in these lines -
line 202 - <View style={[styles.flex1, styles.p1]}>
line 218 - <View style={[styles.flexShrink0, styles.p5]}>
line 223 - containerStyles={[styles.flexReset, styles.flexGrow0, styles.flexShrink0, styles.flexBasisAuto, styles.mb5]}

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

line 202 - - remove the extra padding
line 218 - <View style={[styles.flexShrink0, styles.p5, styles.pt0]}> - update top padding 0
line 223 - containerStyles={[styles.flexReset, styles.flexGrow0, styles.flexShrink0, styles.flexBasisAuto]} - remove the bottom margin.

@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Daily KSv2 labels May 25, 2024
@melvin-bot melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels May 25, 2024
Copy link

melvin-bot bot commented May 27, 2024

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

@ShridharGoel
Copy link
Contributor

@shawnborton Do we need to remove the padding above the button as well? The OP doesn't mention it, I think it looks better if we keep the padding above the button.

@shawnborton
Copy link
Contributor

I think we'd probably remove it, or basically, let's do exactly what we do on the Start a Chat page.

@allgandalf
Copy link
Contributor

Great, thanks @shawnborton ! :) already covered this in the selected proposal :)

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

melvin-bot bot commented May 28, 2024

📣 @GandalfGwaihir 🎉 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 📖

@melvin-bot melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels May 28, 2024
@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Jun 11, 2024
@melvin-bot melvin-bot bot changed the title [$125] Incorrect padding in group invite flow in RHP [HOLD for payment 2024-06-18] [$125] Incorrect padding in group invite flow in RHP Jun 11, 2024
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Jun 11, 2024
Copy link

melvin-bot bot commented Jun 11, 2024

Reviewing label has been removed, please complete the "BugZero Checklist".

Copy link

melvin-bot bot commented Jun 11, 2024

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.81-11 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-06-18. 🎊

For reference, here are some details about the assignees on this issue:

  • @thesahindia requires payment through NewDot Manual Requests
  • @allgandalf requires payment (Needs manual offer from BZ)

Copy link

melvin-bot bot commented Jun 11, 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:

  • [@thesahindia / @allgandalf] The PR that introduced the bug has been identified. Link to the PR:
  • [@thesahindia / @allgandalf] 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:
  • [@thesahindia / @allgandalf] 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:
  • [@thesahindia / @allgandalf] Determine if we should create a regression test for this bug.
  • [@thesahindia / @allgandalf] 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.
  • [@mallenexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

@melvin-bot melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Jun 13, 2024
@melvin-bot melvin-bot bot changed the title [HOLD for payment 2024-06-18] [$125] Incorrect padding in group invite flow in RHP [HOLD for payment 2024-06-20] [HOLD for payment 2024-06-18] [$125] Incorrect padding in group invite flow in RHP Jun 13, 2024
Copy link

melvin-bot bot commented Jun 13, 2024

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.82-4 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-06-20. 🎊

For reference, here are some details about the assignees on this issue:

  • @thesahindia requires payment through NewDot Manual Requests
  • @allgandalf requires payment (Needs manual offer from BZ)

Copy link

melvin-bot bot commented Jun 13, 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:

  • [@thesahindia / @allgandalf] The PR that introduced the bug has been identified. Link to the PR:
  • [@thesahindia / @allgandalf] 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:
  • [@thesahindia / @allgandalf] 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:
  • [@thesahindia / @allgandalf] Determine if we should create a regression test for this bug.
  • [@thesahindia / @allgandalf] 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.
  • [@mallenexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

@thesahindia
Copy link
Member

thesahindia commented Jun 17, 2024

It came from #39757. It was a big PR and this issue was hard to prevent. I don't think we need the checklist here. Also no need for a test case.

@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Jun 18, 2024
@mallenexpensify
Copy link
Contributor

Contributor: @allgandalf paid $125 via Upwork
Contributor+: @thesahindia owed $125 via NewDot

Thanks!

@JmillsExpensify
Copy link

$125 approved for @thesahindia

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 External Added to denote the issue can be worked on by a contributor
Projects
None yet
Development

No branches or pull requests