Bulk move expenses to a new report by koko57 · Pull Request #71778 · Expensify/App

koko57 · 2025-10-02T14:18:32Z

Explanation of Change

Fixed Issues

$ #68995
PROPOSAL:

Tests

If the user has no group workspace at all --> Don't show the Move Expenses option

Prerequisites: user has no workspace, has selfDM

Create a few tracked expenses in the selfDM
Go to reports page
Select the unreported expenses
Click "X selected" button
Verify that you do not see Move Expenses option in the popover menu

If the user has a default group workspace --> Show the option and create the report in the active policy

Prerequisites: user has a default workspace, has selfDM

Create a few tracked expenses in the selfDM
Go to reports page
Select the unreported expenses (you might have to clear the filters and/or select Status: Unreported)
Click "X selected" button
Verify that you do see Move Expenses option in the popover menu
Click Move Expenses
Verify that you see Create Report button with the active workspace name as the secondary text
Click Create Report
Verify that the new report is created, you're redirected to the new report and the expenses are moved there

NOTE: Create Report button should also appear when moving reported expenses and should work the same way as for unreported expenses

-> Repeat each step from the test steps above but this time select reported expenses

If the user doesn't have an active workspace but has only one group workspace --> Show the option and create the report in that workspace

Prerequisites: user has only one workspace (is the owner or invitee), has selfDM

Create a few tracked expenses in the selfDM
Go to reports page
Select the unreported expenses (you might have to clear the filters and/or select Status: Unreported)
Click "X selected" button
Verify that you do see Move Expenses option in the popover menu
Click Move Expenses
Verify that you see Create Report button with the workspace name as the secondary text
Click Create Report
Verify that the new report is created, you're redirected to the new report and the expenses are moved there

NOTE: Create Report button should also appear when moving reported expenses and should work the same way as for unreported expenses

-> Repeat each step from the test steps above but this time select reported expenses

If the user has no active workspace but has multiple group policies --> Show the option and ask the user to pick the workspace where the new report should be created

Prerequisites: user has several workspaces - NONE OF THEM DEFAULT (delete or leave the default policy), has selfDM

Create a few tracked expenses in the selfDM
Go to reports page
Select the unreported expenses (you might have to clear the filters and/or select Status: Unreported)
Click "X selected" button
Verify that you do see Move Expenses option in the popover menu
Click Move Expenses
Verify that you see Create Report button with NO secondary text
Click Create Report
Verify that you're redirected to the workspace selector page
Select a workspace
Verify that the new report is created in the selected workspace, you're redirected to the new report and the expenses are moved there

NOTE: Create Report button should also appear when moving reported expenses and should work the same way as for unreported expenses

-> Repeat each step from the test steps above but this time select reported expenses

Verify that no errors appear in the JS console

Offline tests

n/a

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Same as tests

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

Screen.Recording.2025-10-02.at.16.16.28.mp4

Screen.Recording.2025-10-02.at.16.15.08.mp4

Screen.Recording.2025-10-02.at.16.13.18.mp4

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2025-10-02.at.15.51.51.mp4

Screen.Recording.2025-10-02.at.15.50.21.mp4

Screen.Recording.2025-10-02.at.15.44.40.mp4

MacOS: Desktop

melvin-bot · 2025-10-02T14:18:39Z

@parasharrajat Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

codecov · 2025-10-02T14:29:27Z

Codecov Report

❌ Patch coverage is 30.23256% with 30 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/pages/NewReportWorkspaceSelectionPage.tsx	0.00%	16 Missing ⚠️
...rc/pages/Search/SearchTransactionsChangeReport.tsx	0.00%	4 Missing ⚠️
...es/iou/request/step/IOURequestEditReportCommon.tsx	66.66%	3 Missing ⚠️
src/hooks/usePolicyForMovingExpenses.ts	71.42%	2 Missing ⚠️
src/ROUTES.ts	0.00%	1 Missing ⚠️
src/libs/ReportUtils.ts	66.66%	1 Missing ⚠️
src/libs/SearchUIUtils.ts	0.00%	1 Missing ⚠️
src/pages/Search/EmptySearchView.tsx	0.00%	1 Missing ⚠️
...es/home/sidebar/FloatingActionButtonAndPopover.tsx	0.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

parasharrajat · 2025-10-02T19:33:13Z

src/hooks/usePolicyForMovingExpenses.ts

+    });
+
+    const session = useSession();
+    const userPolicies = Object.values(allPolicies ?? {}).filter((policy) => isPolicyMemberWithoutPendingDelete(session?.email, policy) && policy?.type !== CONST.POLICY.TYPE.PERSONAL);


Suggested change

const userPolicies = Object.values(allPolicies ?? {}).filter((policy) => isPolicyMemberWithoutPendingDelete(session?.email, policy) && policy?.type !== CONST.POLICY.TYPE.PERSONAL);

const userPolicies = Object.values(allPolicies ?? {}).filter((policy) => isPolicyMemberWithoutPendingDelete(session?.email, policy) && isPaidGroupPolicy(policy));

Even though it is same but this one is more declarative.

parasharrajat · 2025-10-02T19:36:49Z

src/hooks/usePolicyForMovingExpenses.ts

+        return {policyForMovingExpensesID: undefined, policyForMovingExpenses: undefined, shouldSelectPolicy: true};
+    }
+
+    return {policyForMovingExpensesID: undefined, policyForMovingExpenses: undefined, shouldSelectPolicy: false};


Suggested change

return {policyForMovingExpensesID: undefined, policyForMovingExpenses: undefined, shouldSelectPolicy: false};

return {policyForMovingExpenses: undefined, shouldSelectPolicy: false};

Seems unnecessary when we are exporting policyForMovingExpenses

in some cases we will need the id only so why not export it

We can get it from policyForMovingExpenses variable, so I would keep one source

I don't like the optional chaining everywhere when we really don't need to use the whole object

If it won't be used extensively, I will remove it

parasharrajat · 2025-10-02T19:39:15Z

src/libs/ReportUtils.ts

+    // temporary check for Search Page only
+    isSearchPageOption?: boolean,


Can you please add more explanation about this temporary check? Will we remove it in future? if so, please add todo for cleanup.

Not sure yet if we will remove it - if we will have the upgrade path from the Search Page it will no longer be necessary. But it of course will depend on the Expensify team decision

parasharrajat · 2025-10-02T19:56:57Z

src/libs/ReportUtils.ts

+        const isUserWorkspaceMember = Object.values(allPolicies ?? {}).find(
+            (policyItem) => policyItem?.employeeList?.[currentUserEmail ?? ''] && policyItem?.type !== CONST.POLICY.TYPE.PERSONAL,
+        );


We should use something similar to getActivePolicies here but you can check other methods in policyutils or create more suitable one.

it will probably be changed later, so I don't want to create an util now that won't be used later

But we need to check for non-pending deletion policy here too, so we should use either getActivePolicies or add code here.

parasharrajat · 2025-10-02T19:59:29Z

src/pages/NewReportWorkspaceSelectionPage.tsx


    const [policies, fetchStatus] = useOnyx(ONYXKEYS.COLLECTION.POLICY, {canBeMissing: true});
    const currentUserPersonalDetails = useCurrentUserPersonalDetails();
+    const isASAPSubmitBetaEnabled = Permissions.isBetaEnabled(CONST.BETAS.ASAP_SUBMIT, allBetas);


Use usePermissions hook.

parasharrajat · 2025-10-02T20:11:55Z

src/pages/iou/request/step/IOURequestEditReportCommon.tsx

Changes of this file is not used in this PR/change, so we should not add them here.

how they are not used? without this changes you wouldn't see the create report button when moving expenses from Search page

Oops, my bad, I didn't see that it is used in.

koko57 · 2025-10-03T08:16:54Z

@parasharrajat comments addressed

parasharrajat · 2025-10-03T09:21:22Z

Thanks. Checking...

parasharrajat · 2025-10-03T09:33:47Z

src/libs/ReportUtils.ts

        // Unreported transaction from OldDot can have the reportID as an empty string
        const isUnreportedExpense = !transaction?.reportID || transaction?.reportID === CONST.REPORT.UNREPORTED_REPORT_ID;

+        const isUserWorkspaceMember = getActivePolicies(allPolicies ?? {}, currentUserEmail).length;


This does not check for paid policies so we need to check for that too.

@parasharrajat addressed!

parasharrajat · 2025-10-03T10:09:09Z

I see that this PR is enabling create report option for expense reports as well. is this expected/ @koko57

03.10.2025_15.38.40_REC.mp4

parasharrajat · 2025-10-03T10:14:20Z

BUG: In test 2 and 3, user does not move to created report after expense are moved. it stays on reports page.

on staging, user remain on reports page for both expenses reports. There is no create report button there.

koko57 · 2025-10-03T10:14:47Z

I see that this PR is enabling create report option for expense reports as well. is this expected/ @koko57

03.10.2025_15.38.40_REC.mp4

I will check it

koko57 · 2025-10-03T10:21:08Z

I think it would be hard to differentiate - I would need to check if all the selected transactions and this is what I have

So I guess I would need much coplex logix to check if only unreported transactions are selected

@cristipaval can we ship with this button on the Search Page only? We're eventually adding the support for reported expenses in the next PR

cristipaval · 2025-10-03T11:01:15Z

I see that this PR is enabling create report option for expense reports as well. is this expected/ @koko57

Thanks for double-checking the expected behavior, @parasharrajat!

Yes, as long as it behaves correctly, let it be enabled for reported expenses as well. So we always want the Create Report as an option for the Move expenses action.

koko57 · 2025-10-03T11:09:00Z

@parasharrajat are you sure that for test 2 and 3? it only navigates to the report when selecting the workspace from the selector, I will block that

koko57 · 2025-10-03T11:10:53Z

user should now stay on Reports Page after all the actions

parasharrajat · 2025-10-03T11:27:39Z

So I guess I would need much coplex logix to check if only unreported transactions are selected

I think we can check for reports sub tab as reports sub tab does not show unreported expenses.. If that is selected do you show create Report in Move expense. @koko57

koko57 · 2025-10-03T11:36:04Z

So I guess I would need much coplex logix to check if only unreported transactions are selected

I think we can check for reports sub tab as reports sub tab does not show unreported expenses.. If that is selected do you show create Report in Move expense. @koko57

@parasharrajat not sure, but anyway @cristipaval said that it is expected - we want the button for both reported and unreported

parasharrajat · 2025-10-03T11:37:20Z

Sure, I will check that too. Can you please add that flow in your test steps as well?

koko57 · 2025-10-03T11:37:42Z

@parasharrajat done! ready for the review

koko57 · 2025-10-03T11:45:46Z

@parasharrajat such a note will do?

NOTE: Create Report button should also appear when moving reported expenses and should work the same way as for unreported expenses

-> Repeat each step from the test steps above but this time select reported expenses

I don't want to repeat all the steps 😅

parasharrajat · 2025-10-03T12:13:31Z

May be just add notes under all cases that should work with reported one. You can say to repeat steps in the note.

parasharrajat · 2025-10-03T15:35:47Z

Bug: The Report expenses does not show create report button on Move expenses.

Open any report which have 2 or more expenses.
Select expenses > more > move expeneses.

koko57 · 2025-10-03T15:40:16Z

Bug: The Report expenses does not show create report button on Move expenses.

Open any report which have 2 or more expenses.

Select expenses > more > move expeneses.

@parasharrajat thanks for pointing this out - I guess this is because we're enabling moving expenses from the search page - the option you mention will come in the second PR

if you start from the expense report you're redirected to a different page

parasharrajat · 2025-10-03T15:42:17Z

When I open a report from reports page too, I don't this option.

the option you mention will come in the second PR

Ok, thanks for confirming. Should we add a note on the test steps so that QA does not report it as a bug?

koko57 · 2025-10-03T15:43:01Z

When I open a report from reports page too, I don't this option.

the option you mention will come in the second PR

Ok, thanks for confirming.

can you show me a recording? with a visible url? or give me exact test steps?

koko57 · 2025-10-03T15:48:01Z

if you have such url we don't show the button yet, only for /search/move-transactions

parasharrajat · 2025-10-03T16:17:37Z

Here is the vid.

Steps;

Go to reports page,
Select reports sub tab.
click on a report to open it.
Select and move expenses.

03.10.2025_21.46.32_REC.mp4

parasharrajat · 2025-10-03T16:18:59Z

Screenshots

🔲 iOS / native

03.10.2025_21.32.10_REC.mp4

🔲 iOS / Safari

03.10.2025_21.51.19_REC.mp4

🔲 MacOS / Desktop

03.10.2025_21.42.15_REC.mp4

🔲 MacOS / Chrome

03.10.2025_20.59.58_REC.mp4

🔲 Android / Chrome

03.10.2025_21.22.18_REC.mp4

🔲 Android / native

03.10.2025_21.20.06_REC.mp4

03.10.2025_21.15.41_REC.mp4

parasharrajat

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

🎀 👀 🎀 C+ reviewed

koko57 · 2025-10-03T17:32:13Z

Here is the vid.

Steps;

Go to reports page,

Select reports sub tab.

click on a report to open it.

Select and move expenses.

03.10.2025_21.46.32_REC.mp4

yeah, exactly - the url is edit/submit/report later - it's handled in the second PR
thanks for checking!

but actually funny that it navigates there not to the search/move-expenses

OSBotify · 2025-10-03T19:13:13Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2025-10-06T20:12:40Z

🚀 Deployed to staging by https://github.com/cristipaval in version: 9.2.24-0 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

OSBotify · 2025-10-07T15:20:02Z

🚀 Deployed to staging by https://github.com/cristipaval in version: 9.2.26-0 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

OSBotify · 2025-10-08T04:51:33Z

🚀 Deployed to production by https://github.com/lakchote in version: 9.2.26-7 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

koko57 added 3 commits October 2, 2025 15:56

fix: create report button

0abbc01

feat: add workspace selector

0a006da

feat: create new report after selecting workspace

0e99dfa

koko57 requested a review from a team as a code owner October 2, 2025 14:18

melvin-bot bot requested a review from parasharrajat October 2, 2025 14:18

melvin-bot bot assigned koko57 Oct 2, 2025

melvin-bot bot removed the request for review from a team October 2, 2025 14:18

cristipaval changed the title ~~Bulk move expenses + create report~~ Bulk move expenses to a new report Oct 2, 2025

fix: remove file

47991e1

parasharrajat suggested changes Oct 2, 2025

View reviewed changes

fix: apply requested change

cd13c25

fix: apply requested change

97e9663

koko57 requested a review from parasharrajat October 3, 2025 09:15

parasharrajat reviewed Oct 3, 2025

View reviewed changes

fix: check for paid policy

ddf4a7f

koko57 added 2 commits October 3, 2025 12:27

fix: prettier

a50b3df

Merge branch 'main' into feat/68995-bulk-move-expenses-v2

c750399

fix: do not navigate to report page when moving expense

aff4d49

fix: minor fix

c9fdf59

fix: navigate back to the search page

89ba4c4

parasharrajat approved these changes Oct 3, 2025

View reviewed changes

melvin-bot bot requested a review from cristipaval October 3, 2025 16:19

cristipaval approved these changes Oct 3, 2025

View reviewed changes

cristipaval merged commit 21d01a5 into Expensify:main Oct 3, 2025
22 checks passed

parasharrajat mentioned this pull request Oct 6, 2025

Create report from reported expense #71808

Merged

54 tasks

OSBotify mentioned this pull request Oct 6, 2025

Deploy Checklist: New Expensify 2025-10-06 #71926

Closed

73 tasks

This was referenced Oct 6, 2025

[Unreported] Reports - "Category no longer valid" is shown briefly after the expense is moved to new report #71931

Closed

[Due for payment 2025-10-15] Reports - Paywall is not shown when creating a new report from Report list RHP on Reports #71939

Closed

jponikarchuk mentioned this pull request Oct 7, 2025

[Due for payment 2026-01-23] [Unreported] Expense - Violations are only seen on preview when moving track expense to new report offline #71950

Closed

8 tasks

melvin-bot bot mentioned this pull request Oct 8, 2025

[Due for payment 2025-10-15] [Unreported] [$250] [CRITICAL] Bulk move unreported expenses to a new report #68995

Closed

lanitochka17 mentioned this pull request Oct 29, 2025

[$250] Reports - Create report button does not show upgrade page when account has no workspace #73762

Open

16 tasks

	const userPolicies = Object.values(allPolicies ?? {}).filter((policy) => isPolicyMemberWithoutPendingDelete(session?.email, policy) && policy?.type !== CONST.POLICY.TYPE.PERSONAL);
	const userPolicies = Object.values(allPolicies ?? {}).filter((policy) => isPolicyMemberWithoutPendingDelete(session?.email, policy) && isPaidGroupPolicy(policy));

	return {policyForMovingExpensesID: undefined, policyForMovingExpenses: undefined, shouldSelectPolicy: false};
	return {policyForMovingExpenses: undefined, shouldSelectPolicy: false};

		// temporary check for Search Page only
		isSearchPageOption?: boolean,

Conversation

koko57 commented Oct 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

If the user has no group workspace at all --> Don't show the Move Expenses option

If the user has a default group workspace --> Show the option and create the report in the active policy

If the user doesn't have an active workspace but has only one group workspace --> Show the option and create the report in that workspace

If the user has no active workspace but has multiple group policies --> Show the option and ask the user to pick the workspace where the new report should be created

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Oct 2, 2025

Uh oh!

codecov bot commented Oct 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

koko57 commented Oct 3, 2025

Uh oh!

parasharrajat commented Oct 3, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

parasharrajat commented Oct 3, 2025

Uh oh!

parasharrajat commented Oct 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

koko57 commented Oct 3, 2025

Uh oh!

koko57 commented Oct 3, 2025

Uh oh!

cristipaval commented Oct 3, 2025

Uh oh!

koko57 commented Oct 3, 2025

Uh oh!

koko57 commented Oct 3, 2025

Uh oh!

parasharrajat commented Oct 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

koko57 commented Oct 3, 2025

Uh oh!

parasharrajat commented Oct 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

koko57 commented Oct 2, 2025 •

edited

Loading

codecov bot commented Oct 2, 2025 •

edited

Loading

parasharrajat commented Oct 3, 2025 •

edited

Loading

parasharrajat commented Oct 3, 2025 •

edited

Loading

parasharrajat commented Oct 3, 2025 •

edited

Loading

parasharrajat commented Oct 3, 2025 •

edited

Loading

koko57 commented Oct 3, 2025 •

edited

Loading

parasharrajat commented Oct 3, 2025 •

edited

Loading

parasharrajat commented Oct 3, 2025 •

edited

Loading

koko57 commented Oct 3, 2025 •

edited

Loading