Skip to content

[Due for payment 2025-10-27] [Due for payment 2025-10-21] Remove Onyx.connect() for the key: ONYXKEYS.COLLECTION.POLICY_RECENTLY_USED_CATEGORIES in src/libs/actions/Policy/Category.ts #66557

Closed

Description

@tgolen

This is part of deprecating Onyx.connect. Parent Issue

Details

  • Module: src/libs/actions/Policy/Category.ts
  • Onyx Key: ONYXKEYS.COLLECTION.POLICY_RECENTLY_USED_CATEGORIES
  • Reference: Line 75: ONYXKEYS.COLLECTION.POLICY_RECENTLY_USED_CATEGORIES

Be sure to refactor methods using test driven development:

  1. Create a unit test for methods before refactoring
  2. Refactor the methods
  3. Ensure the unit test still runs after refactoring
  4. Reinforce the unit testing with a functional test and a QA test
  5. Once you are done, decrease the number of allowable ESLint warnings here to equal the number of Onyx.connect references remaining in the code
Issue OwnerCurrent Issue Owner: @dylanexpensify

Activity

  1. self-assigned this
    on Jul 16, 2025
  2. added
    ImprovementItem broken or needs improvement.
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 16, 2025
  3. tgolen commented on Jul 16, 2025

    @tgolen
    ContributorAuthor

    Warning

    DO NOT POST PROPOSALS ON THIS ISSUE!!

    Bug-Zero Instructions

    • This issue is CLOSED for proposals
    • It is a special issue and part of a bigger project
    • A contributor will be manually assigned to work on this issue and they do not need to submit a proposal
    • The bug-zero person only needs to take care of payments to the contributor for the PR and the C+ for reviews
    • There do not need to be any regression tests added or updated since this is only refactoring and shouldn't change any existing functionality
  4. melvin-bot commented on Jul 16, 2025

    @melvin-bot

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

  5. added and removed on Jul 16, 2025
  6. melvin-bot commented on Jul 30, 2025

    @melvin-bot

    @tgolen @dylanexpensify this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

  7. DylanDylann commented on Aug 2, 2025

    @DylanDylann
    Contributor

    I and @ikevin127 will work on this issue. @adelekennedy @tgolen could you help to assign us?

  8. 21 remaining items

  9. dylanexpensify commented on Oct 20, 2025

    @dylanexpensify
    Contributor

    Payment summary:

    Contributor: @DylanDylann $250 via NewDot
    Contributor+: @ikevin127 $250 via NewDot

    Please apply/request!

  10. changed the title [-][Due for payment 2025-10-21] Remove `Onyx.connect()` for the key: `ONYXKEYS.COLLECTION.POLICY_RECENTLY_USED_CATEGORIES` in `src/libs/actions/Policy/Category.ts`[/-] [+][Due for payment 2025-10-27] [Due for payment 2025-10-21] Remove `Onyx.connect()` for the key: `ONYXKEYS.COLLECTION.POLICY_RECENTLY_USED_CATEGORIES` in `src/libs/actions/Policy/Category.ts`[/+] on Oct 20, 2025
  11. melvin-bot commented on Oct 20, 2025

    @melvin-bot

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

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

    • @ikevin127 requires payment through NewDot Manual Requests
    • @DylanDylann requires payment through NewDot Manual Requests
  12. melvin-bot commented on Oct 20, 2025

    @melvin-bot

    @ikevin127 / @DylanDylann @dylanexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  13. dylanexpensify commented on Oct 21, 2025

    @dylanexpensify
    Contributor

    Payment coming up

  14. ikevin127 commented on Oct 25, 2025

    @ikevin127
    Contributor

    🟢 No need for BZ Checklist as this issue is part of a refactoring effort (see above BZ Instructions).
    ⌛ Awaiting payment summary confirmation for ND requests.

    ♻️ ...there's only 1 / final payment for this issue coming up on 2025-10-27 from the part 3 pull request which was deployed.

  15. garrettmknight commented on Nov 1, 2025

    @garrettmknight
    Contributor

    $250 approved for @ikevin127

  16. trjExpensify commented on Dec 5, 2025

    @trjExpensify
    Contributor

    approved $250 for @DylanDylann

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.DailyKSv2EngineeringImprovementItem broken or needs improvement.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions