[Due for payment 2025-03-10] [$125] Refactor buildOnyxDataForTrackExpense to use a parameter object

[neil-marcellini]

As part of the tracking issue, and as advised in its description, refactor buildOnyxDataForTrackExpense to use a parameter object.

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021893020095201958566
• Upwork Job ID: 1893020095201958566
• Last Price Increase: 2025-02-21
• Automatic offers:
• FitseTLT | Contributor | 106227062

Issue Owner

Current Issue Owner: @greg-schroeder

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021893020095201958566

[melvin-bot]

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

[melvin-bot]

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

[FitseTLT]

Proposal

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

Refactor buildOnyxDataForTrackExpense to use a parameter object

What is the root cause of that problem?

Refactor

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

Refactor buildOnyxDataForTrackExpense

to use object params also updating the approriate type and accordingly pass the appropriate argument in the instances we are using it

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

N / A

What alternative solutions did you explore? (Optional)

[melvin-bot]

Upwork job price has been updated to $125