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-10-14] Task - Green dot is not on the same line as the caret #50151

Closed
6 tasks done
IuliiaHerets opened this issue Oct 3, 2024 · 15 comments
Closed
6 tasks done
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Engineering Weekly KSv2

Comments

@IuliiaHerets
Copy link

IuliiaHerets commented Oct 3, 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: 9.0.44-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to DM.
  3. Assign a task to yourself.

Expected Result:

The green dot should be on the same line as the caret (production behavior).

Actual Result:

The green dot is not on the same line as the caret.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6623234_1727962473551.task.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @abekkala
@IuliiaHerets IuliiaHerets added DeployBlockerCash This issue or pull request should block deployment Bug Something is broken. Auto assigns a BugZero manager. labels Oct 3, 2024
Copy link

melvin-bot bot commented Oct 3, 2024

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

@melvin-bot melvin-bot bot added the Daily KSv2 label Oct 3, 2024
Copy link
Contributor

github-actions bot commented Oct 3, 2024

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

  1. Identify the pull request that introduced this issue and revert it.
  2. Find someone who can quickly fix the issue.
  3. Fix the issue yourself.

@melvin-bot melvin-bot bot removed the Hourly KSv2 label Oct 3, 2024
Copy link

melvin-bot bot commented Oct 3, 2024

Triggered auto assignment to @rlinoz (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

@Nodebrute
Copy link
Contributor

Nodebrute commented Oct 3, 2024

Edited by proposal-police: This proposal was edited at 2024-10-03 14:48:44 UTC.

Proposal

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

Green dot is not on the same line as the caret

What is the root cause of that problem?

We see this error only when task has assignee because we are not adding iconWrapperStyle to this

{shouldShowGreenDotIndicator && (
<View style={styles.ml2}>
<Icon
src={Expensicons.DotIndicator}
fill={theme.success}
/>
</View>

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

We should pass iconWrapperStyle in styles here

{shouldShowGreenDotIndicator && (
<View style={styles.ml2}>
<Icon
src={Expensicons.DotIndicator}
fill={theme.success}
/>
</View>

    <View style={[styles.ml2,iconWrapperStyle]}>
                        <Icon
                            src={Expensicons.DotIndicator}
                            fill={theme.success}
                        />
                    </View>

Other minor styling can be adjusted in the pr
Screenshot 2024-10-03 at 7 43 00 PM

What alternative solutions did you explore? (Optional)

Or we can remove iconWrapperStyle from here to fix this

additionalStyles={iconWrapperStyle}

@rlinoz
Copy link
Contributor

rlinoz commented Oct 3, 2024

This PR introduced the issue: #49686, although it fixes worst ones 😄

cc: @bernhardoj @rayane-djouah

@rlinoz
Copy link
Contributor

rlinoz commented Oct 3, 2024

Also I don't think it needs to be a blocker, as it is a minor style issue.

@rlinoz rlinoz removed the DeployBlockerCash This issue or pull request should block deployment label Oct 3, 2024
@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Daily KSv2 labels Oct 3, 2024
@bernhardoj
Copy link
Contributor

PR is up

@rayane-djouah
Copy link
Contributor

Thanks @bernhardoj !

@ChavdaSachin
Copy link
Contributor

Proposal

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

Task - Green dot is not on the same line as the caret

What is the root cause of that problem?

We are using dynamic styles for surrounding elements, while not for greenDot.

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

Option 1.

  • Move GreenDotIndicator element inside this view, This way We take advantage of styles.mr2 in this view for better spacing between greendot and arrow icon.

    <View style={[styles.flex1, styles.flexRow, styles.alignItemsStart, styles.mr2]}>
    <View style={iconWrapperStyle}>
    <Checkbox
    style={[styles.mr2]}
    isChecked={isTaskCompleted}
    disabled={!Task.canModifyTask(taskReport, currentUserPersonalDetails.accountID) || !Task.canActionTask(taskReport, currentUserPersonalDetails.accountID)}
    onPress={Session.checkIfActionIsAllowed(() => {
    if (isTaskCompleted) {
    Task.reopenTask(taskReport);
    } else {
    Task.completeTask(taskReport);
    }
    })}
    accessibilityLabel={translate('task.task')}
    />
    </View>
    {hasAssignee && (
    <Avatar
    containerStyles={[styles.mr2, isTaskCompleted ? styles.opacitySemiTransparent : undefined]}
    source={avatar}
    size={avatarSize}
    avatarID={taskAssigneeAccountID}
    type={CONST.ICON_TYPE_AVATAR}
    />
    )}
    <Text style={titleStyle}>{taskTitle}</Text>
    </View>

    {shouldShowGreenDotIndicator && (
    <View style={styles.ml2}>
    <Icon
    src={Expensicons.DotIndicator}
    fill={theme.success}
    />
    </View>
    )}

  • Additionally apply iconWrapperStyle to greenDot indicator icon.

    <Icon
        src={Expensicons.DotIndicator}
        fill={theme.success}
        additionalStyles={iconWrapperStyle}
    />

<Icon
src={Expensicons.DotIndicator}
fill={theme.success}
/>

Option 2.
If we don't want to move greenDot inside view as I suggested, then we should remove styles.ml2 style and hence wrapping view for greenDot icon. (We have ml2 for greenDot and mr2 for task title due which task title is shrinking too much without need)

Just centering greenDot option 1 (even space on both side) option 2 (consuming less space from task title)
Screenshot 2024-10-03 at 9 31 33 PM Screenshot 2024-10-03 at 9 32 40 PM Screenshot 2024-10-03 at 9 32 05 PM

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Oct 3, 2024
@rayane-djouah
Copy link
Contributor

PR #50165 ready to be merged

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Daily KSv2 labels Oct 7, 2024
@melvin-bot melvin-bot bot changed the title Task - Green dot is not on the same line as the caret [HOLD for payment 2024-10-14] Task - Green dot is not on the same line as the caret Oct 7, 2024
Copy link

melvin-bot bot commented Oct 7, 2024

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

@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Oct 7, 2024
Copy link

melvin-bot bot commented Oct 7, 2024

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.45-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-10-14. 🎊

Copy link

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

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

@rayane-djouah
Copy link
Contributor

No payment is due. We can close this issue.

@rlinoz
Copy link
Contributor

rlinoz commented Oct 8, 2024

Nice, thanks!

This is fixed by #50281

@rlinoz rlinoz closed this as completed Oct 8, 2024
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. Engineering Weekly KSv2
Projects
None yet
Development

No branches or pull requests

7 participants