You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[$250] Refactor shareTrackedExpense to use a parameter object #54466
Please re-state the problem that we are trying to solve in this issue.
Refactor
What is the root cause of that problem?
NA
What changes do you think we should make in order to solve the problem?
Refactor IOU.shareTrackedExpense function.
Minimize Input fields and cluster input params in sensible sub-objects.
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
No Changes.
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
changed the title [-]Refactor shareTrackedExpense to use a parameter object[/-][+][$250] Refactor shareTrackedExpense to use a parameter object[/+]on Dec 23, 2024
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:
Where bug was reported:
2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
2b. Reported on staging (eg. found during regression or PR testing)
2d. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[Contributor] 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:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
ChavdaSachin commentedon Dec 23, 2024
Proposal
Please re-state the problem that we are trying to solve in this issue.
Refactor
What is the root cause of that problem?
NA
What changes do you think we should make in order to solve the problem?
Refactor IOU.shareTrackedExpense function.
Minimize Input fields and cluster input params in sensible sub-objects.
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
No Changes.
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
[-]Refactor shareTrackedExpense to use a parameter object[/-][+][$250] Refactor shareTrackedExpense to use a parameter object[/+]melvin-bot commentedon Dec 23, 2024
Job added to Upwork: https://www.upwork.com/jobs/~021871214955675002445
melvin-bot commentedon Dec 23, 2024
Triggered auto assignment to @MitchExpensify (
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.melvin-bot commentedon Dec 23, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak (
External)melvin-bot commentedon Dec 27, 2024
@eVoloshchak, @neil-marcellini, @MitchExpensify, @ChavdaSachin Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
15 remaining items
ChavdaSachin commentedon Jan 30, 2025
@neil-marcellini default IDs are already implemented Here, we are free to close this issue as soon as 7 days regresion period is over for this PR.
ChavdaSachin commentedon Feb 3, 2025
@neil-marcellini could you please send upwork offers and mark this GH as pending for payment.
check my previous comment.
MitchExpensify commentedon Feb 3, 2025
@ChavdaSachin It's my role to make sure the Upwork offers are sent. Has the PR hit production yet? The offers should go out automatically once it has
ChavdaSachin commentedon Feb 4, 2025
Pr did hit production 7 days back
MitchExpensify commentedon Feb 4, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] 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:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
MitchExpensify commentedon Feb 4, 2025
Payment summary:
MitchExpensify commentedon Feb 4, 2025
Here is your offer @ChavdaSachin https://www.upwork.com/ab/applicants/1886926850410966330/suggested
ChavdaSachin commentedon Feb 5, 2025
Accepted
MitchExpensify commentedon Feb 5, 2025
Paid, thanks!
eVoloshchak commentedon Feb 19, 2025
BugZero Checklist in #54466 (comment)
This isn't a bug, but rather a code improvement, not sure if this classification applies here
Same as above, not a bug, there is no offending PR
No additional discussion in Slack or regression test are needed either
I'll request through NewDot
JmillsExpensify commentedon Mar 3, 2025
$250 approved for @eVoloshchak