Skip to content

[Partial Payment] Remove Onyx.connect() for the key: ONYXKEYS.PERSONAL_DETAILS_LIST in src/libs/actions/Report.ts #73656

Open

Description

@tgolen

This is part of deprecating Onyx.connect. Parent Issue

Details

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: @parasharrajat

Activity

  1. self-assigned this
    on Oct 28, 2025
  2. tgolen commented on Oct 28, 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
  3. added
    ImprovementItem broken or needs improvement.
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 28, 2025
  4. melvin-bot commented on Oct 28, 2025

    @melvin-bot

    Triggered auto assignment to @muttmuure (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. lorretheboy commented on Oct 28, 2025

    @lorretheboy
    Contributor

    I would happy to help if it opens for external

  6. added and removed on Oct 28, 2025
  7. tgolen commented on Oct 28, 2025

    @tgolen
    ContributorAuthor

    @lorretheboy I'll extend to you the same option I did over here, and just copy my comment:

    Historically, this project has been for a closed group of contributors. However, I would be open to seeing what your proposal would be for this one. If it works out and you are solid and know what you're doing with few instuctions, then perhaps you can work on more of these for us. Can you post a quick proposal for this one, please?

  8. 265 remaining items

  9. added and removed
    ReviewingHas a PR in review
    on Nov 7, 2026
  10. melvin-bot commented on Nov 7, 2026

    @melvin-bot

    @parasharrajat

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.33-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ 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]. If no checklist is needed for this issue, you can click: [no checklist button]

  11. lorretheboy commented on Nov 10, 2026

    @lorretheboy
    Contributor

    Part 10 can be opened for review this by tomorrow

  12. rlinoz commented on Nov 10, 2026

    @rlinoz
    Contributor

    I am going on extended leave soon, and since you are already assigned here I will leave the rest of this one to you @tgolen 🙇

  13. assigned and unassigned on Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringImprovementItem broken or needs improvement.Skip PaymentSkips all the payment process steps for an issue. Use it for fixed-price projects.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions