Skip to content

[HOLD for payment 2023-11-09] [Wave 6: Categories] Design follow up to Tag and Category lists #29574

Closed

Description

@mountiny

Here is an tracking issue to compile feedback and implement improved design for the category and tag list
image

Slack thread

cc @waterim @rezkiy37 @shawnborton

Activity

  1. melvin-bot commented on Oct 13, 2023

    @melvin-bot
  2. self-assigned this
    on Oct 13, 2023
  3. shawnborton commented on Oct 13, 2023

    @shawnborton
    Contributor

    I think something like this would be more ideal:
    CleanShot 2023-10-13 at 12 42 53@2x

    • Each child/sub-category should get an additional 12px of left padding, and this padding is applied to the whole row so that the text has the same left edge
    • There should be 20px of space between each "block" with each block meaning the Search box, the current selection, the Recents block, and then the All block
  4. shawnborton commented on Oct 13, 2023

    @shawnborton
    Contributor

    cc @Expensify/design for thoughts if you have any!

  5. puneetlath commented on Oct 13, 2023

    @puneetlath
    Contributor

    For anything that takes more than two lines, we should just overflow with elipse is that right?

    Also, just FYI, in case this wasn't known, this is how we show a sub-category when it has been selected and you re-enter the list. It's shown at the top with colons to indicate the full selection:
    image
    image

  6. shawnborton commented on Oct 13, 2023

    @shawnborton
    Contributor

    I like that - so show two lines worth of text and truncate after that? That should be plenty I think.

  7. 17 remaining items

  8. changed the title [-][Wave 6: Categories] Design follow up to Tag and Category lists[/-] [+][HOLD for payment 2023-11-09] [Wave 6: Categories] Design follow up to Tag and Category lists[/+] on Nov 2, 2023
  9. melvin-bot commented on Nov 2, 2023

    @melvin-bot

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

  10. melvin-bot commented on Nov 2, 2023

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.94-2 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 2023-11-09. 🎊

    After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

    • External issue reporter
    • Contributor that fixed the issue
    • Contributor+ that helped on the issue and/or PR

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

    • @rezkiy37 does not require payment (Contractor)
  11. melvin-bot commented on Nov 2, 2023

    @melvin-bot

    BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@rezkiy37] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
    • [@puneetlath] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.
  12. mountiny commented on Nov 2, 2023

    @mountiny
    ContributorAuthor

    We will need to pay $500 to @mollfpr for testing and review

  13. puneetlath commented on Nov 6, 2023

    @puneetlath
    Contributor
  14. mollfpr commented on Nov 6, 2023

    @mollfpr
    Contributor

    @puneetlath I'll do a manual request in NewDot. Could you give the payment summary? Thank you!

  15. puneetlath commented on Nov 6, 2023

    @puneetlath
    Contributor

    Ah whoops. Didn't realize you were being paid there now!

    Payment summary:

  16. mountiny commented on Nov 7, 2023

    @mountiny
    ContributorAuthor

    I think we can close now as @mollfpr is paid in Newdot

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 productionNewFeatureSomething to build that is a new item.WeeklyKSv2

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions