Skip to content

[HOLD for payment 2024-07-10] [HOLD for payment 2024-07-02] [$125] Small font updates for Search page #43512

Closed

Description

@shawnborton

We just released our new Search page, but we noticed quite a few font inconsistencies that we want to update.

On desktop:
image

  • Let's use our normal font size (15px) for every column. This means undoing the smaller sizes for things like the To/From columns, or Tax column.
  • Let's use a gap of 8px between the avatar and the From/To names: CleanShot 2024-06-11 at 22 36 22@2x
  • Let's remove any Expensify New Kansas from the table as well

On mobile:
CleanShot 2024-06-11 at 22 37 33@2x

  • Let's only use our normal font size (15px) and our micro font size (11px)
  • Merchant and amount will use the normal font size, everything else gets micro
  • Let's remove the bold style from the from/to, as well as update the spacing to use 8px between avatar and name CleanShot 2024-06-11 at 22 39 42@2x

cc @Expensify/design @luacmartins @iwiznia

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~017822f748f43e483b
  • Upwork Job ID: 1800776935107005435
  • Last Price Increase: 2024-06-12
  • Automatic offers:
    • c3024 | Reviewer | 102708541
Issue OwnerCurrent Issue Owner: @sakluger

Activity

  1. self-assigned this
    on Jun 11, 2024
  2. melvin-bot commented on Jun 11, 2024

    @melvin-bot

    Current assignee @shawnborton is eligible for the Design assigner, not assigning anyone new.

  3. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jun 12, 2024
  4. changed the title [-]Small font updates for Search page[/-] [+][$250] Small font updates for Search page[/+] on Jun 12, 2024
  5. melvin-bot commented on Jun 12, 2024

    @melvin-bot
  6. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jun 12, 2024
  7. melvin-bot commented on Jun 12, 2024

    @melvin-bot

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

  8. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 12, 2024
  9. melvin-bot commented on Jun 12, 2024

    @melvin-bot

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

  10. shawnborton commented on Jun 12, 2024

    @shawnborton
    ContributorAuthor

    Given that these are just small style adjustments, I think we can reduce the price down to $125. Thoughts @sakluger?

  11. truph01 commented on Jun 12, 2024

    @truph01
    Contributor

    @shawnborton I'd volunteer to take this issue. The changes are straight forward so I don't think we need a full proposal detailing the code part for every small change here right?

    Proposal

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

    We want to add some small font updates for Search page

    What is the root cause of that problem?

    This is a new requested feature, not a bug

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

    Just follow the list of changes here #43512 (comment), they are all straight-forward changes

    An example of changes needed for one of the item:

    Let's use our normal font size (15px) for every column. This means undoing the smaller sizes for things like the To/From columns, or Tax column.

    For To/From columns, replace textMicroBold here with textStrong, or create a new textBold style that is similar to textMicroBold but doensn't have these lines

    For Tax column, remove styles.label here. We can add lineHeight: variables.lineHeightLarge, from label if it's still needed (I think we don't need it)

    There're other fields similar to the Tax column like Date, Merchant column

    Let's use a gap of 8px between the avatar and the From/To names:

    Replace styles.gap1 here by styles.gap1. Or remove the styles.gap1 and add pr2 to the Avatar

    Let's remove any Expensify New Kansas from the table as well

    There's Expensify New Kansas font in here in ReportListItem, we can remove styles.textNewKansasNormal (or just the font family).

    There's that font used in the Header too can can be removed like that, but I guess we should not remove the font there.

    Mobile-specific changes (can alternate using isLargeScreenWidth/isSmallScreenWidth):

    Merchant and amount will use the normal font size, everything else gets micro

    Don't use any specific font style for Merchant (remove styles.label) and Amount, but use styles.textMicro for other cells

    Let's remove the bold style from the from/to

    Replace textMicroBold with textMicro here. That means it's bold on Desktop but not mobile, let's consider if they should be consistent (bold or not)

    update the spacing to use 8px between avatar and name

    Covered in desktop changes

    Mobile-specific changes (can alternate using isLargeScreenWidth/isSmallScreenWidth):

    To achieve this, we can add customized styles by adding style prop to cell components like MerchantCell, UserInfoCell. And add the correct style depending on where the cell is rendered in

    What alternative solutions did you explore? (Optional)

  12. 22 remaining items

  13. melvin-bot commented on Jun 25, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.1-19 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-07-02. 🎊

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

  14. melvin-bot commented on Jun 25, 2024

    @melvin-bot

    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:

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

    @sakluger
    Contributor

    Summarizing payment on this issue:

    Contributor: @truph01 $125 - Please apply to the Upwork job: https://www.upwork.com/jobs/~017822f748f43e483b
    Contributor+: @c3024 $125, paid via Upwork

    I don't think we need to complete the BZ checklist for this one because it's just a minor font change.

  16. sakluger commented on Jul 3, 2024

    @sakluger
    Contributor

    @truph01 I found your Upwork profile and sent you an offer: https://www.upwork.com/nx/wm/offer/102974684/

    Could you please let me know once you've accepted the offer? Thanks!

  17. truph01 commented on Jul 3, 2024

    @truph01
    Contributor

    @sakluger Accepted, thanks 🙏 🙏

  18. sakluger commented on Jul 3, 2024

    @sakluger
    Contributor

    Thank you! All paid out 👍

  19. changed the title [-][HOLD for payment 2024-07-02] [$125] Small font updates for Search page[/-] [+][HOLD for payment 2024-07-10] [HOLD for payment 2024-07-02] [$125] Small font updates for Search page[/+] on Jul 3, 2024
  20. melvin-bot commented on Jul 3, 2024

    @melvin-bot

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

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

  21. melvin-bot commented on Jul 3, 2024

    @melvin-bot

    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:

    • [@c3024] The PR that introduced the bug has been identified. Link to the PR:
    • [@c3024] 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:
    • [@c3024] 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:
    • [@c3024] Determine if we should create a regression test for this bug.
    • [@c3024] 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.
    • [@sakluger] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DesignExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions