Remove call to getReportNameValuePairs() in method getChatRoomSubtitle from ReportUtils.ts #68701

mkzie2 · 2025-08-18T21:13:36Z

Explanation of Change

Fixed Issues

$ #67095
PROPOSAL: #67095

Tests

Test Case 1:

Navigate to any workspace chat room (e.g., #announce, #admins,...)
Click the header to open Report Details
Expected: Subtitle should display correctly (workspace name or room description)

Test Case 2:

Navigate to any report
Go to Report Details → Share
Expected: Share page shows correct subtitle

Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as Tests part

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

android.mov

android-1.mov

Android: mWeb Chrome

web-android.mov

web-android-1.mov

iOS: Native

ios.mov

ios-2.mov

iOS: mWeb Safari

web-ios-2.mov

web-ios.mov

MacOS: Chrome / Safari

web-2.mov

web.mov

MacOS: Desktop

desktop.mov

desktop-1.mov

…ssue/67095

melvin-bot · 2025-08-19T18:49:52Z

@DylanDylann 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]

DylanDylann · 2025-08-20T05:55:10Z

src/libs/OptionsListUtils.ts


        hasMultipleParticipants = personalDetailList.length > 1 || result.isChatRoom || result.isPolicyExpenseChat || reportUtilsIsGroupChat(report);
-        subtitle = getChatRoomSubtitle(report, {isCreateExpenseFlow: true});
+        subtitle = getChatRoomSubtitle(report, {isCreateExpenseFlow: true, isReportArchived: !!result.private_isArchived});


In this function, could you please update to use isArchivedReport function for all places?

const isArchivedReport = isArchivedReport(reportNameValuePairs)

DylanDylann · 2025-08-20T05:55:24Z

src/libs/ReportUtils.ts

        return `${getReportSubtitlePrefix(report)}${translateLocal('iou.submitsTo', {name: subtitle ?? ''})}`;
    }

    // This will get removed as part of https://github.com/Expensify/App/issues/59961


Suggested change

// This will get removed as part of https://github.com/Expensify/App/issues/59961

DylanDylann · 2025-08-20T05:56:15Z

src/libs/SidebarUtils.ts

    const isExpense = isExpenseReport(report);
    const hasMultipleParticipants = participantPersonalDetailList.length > 1 || result.isChatRoom || result.isPolicyExpenseChat || isExpense;
-    const subtitle = getChatRoomSubtitle(report);
+    const subtitle = getChatRoomSubtitle(report, {isReportArchived: !!result.private_isArchived});


In this function, could you please update to use isArchivedReport function for all places?

const isArchivedReport = isArchivedReport(reportNameValuePairs)

DylanDylann · 2025-08-20T05:58:28Z

src/pages/home/HeaderView.tsx

    // Use sorted display names for the title for group chats on native small screen widths
    const title = getReportName(reportHeaderData, policy, parentReportAction, personalDetails, invoiceReceiverPolicy);
-    const subtitle = getChatRoomSubtitle(reportHeaderData);
+    const subtitle = getChatRoomSubtitle(reportHeaderData, {isReportArchived});


isReportArchived should be checked for reportHeaderData. The current isReportArchived is the check for report

DylanDylann · 2025-08-20T05:59:34Z

src/libs/actions/Task.ts

        subtitle = LocalePhoneNumber.formatPhoneNumber(login || displayName);
    } else {
-        subtitle = ReportUtils.getChatRoomSubtitle(report) ?? '';
+        const reportNameValuePair = reportNameValuePairs?.[`${ONYXKEYS.COLLECTION.REPORT_NAME_VALUE_PAIRS}${report?.reportID}`];


In this function, please replace reportNameValuePairs param with isReportArchived param

DylanDylann · 2025-08-20T06:04:27Z

src/pages/tasks/NewTaskPage.tsx

    const [task] = useOnyx(ONYXKEYS.TASK, {canBeMissing: true});
    const [reports] = useOnyx(ONYXKEYS.COLLECTION.REPORT, {canBeMissing: true});
    const [personalDetails] = useOnyx(ONYXKEYS.PERSONAL_DETAILS_LIST, {canBeMissing: false});
+    const [reportNameValuePairs] = useOnyx(ONYXKEYS.COLLECTION.REPORT_NAME_VALUE_PAIRS, {canBeMissing: true});


Please use useReportIsArchived hook

DylanDylann · 2025-08-20T06:04:58Z

src/libs/ReportUtils.ts

 * Get either the policyName or domainName the chat is tied to
 */
-function getChatRoomSubtitle(report: OnyxEntry<Report>, config: GetChatRoomSubtitleConfig = {isCreateExpenseFlow: false}): string | undefined {
+function getChatRoomSubtitle(report: OnyxEntry<Report>, config: GetChatRoomSubtitleConfig = {isCreateExpenseFlow: false, isReportArchived: false}): string | undefined {


Please add UTs for this function to cover new param

mkzie2 · 2025-08-21T15:57:33Z

Hi @DylanDylann, I have updated the PR to address all your comments. Please check again. Thanks

DylanDylann · 2025-08-22T03:33:33Z

src/libs/SidebarUtils.ts

+                getWelcomeMessage(report, policy, localeCompare, isReportArchived).messageText || translateLocal('report.noActivityYet'),
            );
        }
        if (shouldShowLastActorDisplayName(report, lastActorDetails, lastAction) && !isArchivedReport(reportNameValuePairs)) {


using the new variable here

DylanDylann · 2025-08-22T03:36:00Z

src/pages/home/HeaderView.tsx

    const [lastDayFreeTrial] = useOnyx(ONYXKEYS.NVP_LAST_DAY_FREE_TRIAL, {canBeMissing: true});
    const [account] = useOnyx(ONYXKEYS.ACCOUNT, {canBeMissing: true});
    const [reportNameValuePairs] = useOnyx(`${ONYXKEYS.COLLECTION.REPORT_NAME_VALUE_PAIRS}${report?.reportID}`, {canBeMissing: true});
+    const [reportNameValuePairsForParentReport] = useOnyx(`${ONYXKEYS.COLLECTION.REPORT_NAME_VALUE_PAIRS}${parentReport?.reportID}`, {canBeMissing: true});


In the component, please use useReportIsArchived hook

DylanDylann · 2025-08-22T03:38:06Z

src/pages/tasks/NewTaskPage.tsx

+        () => (task?.shareDestination ? getShareDestination(task.shareDestination, reports, personalDetails, localeCompare, isReportArchived) : undefined),
+        [task?.shareDestination, reports, personalDetails, localeCompare, isReportArchived],


task.shareDestination never be archived (isReportArchived will be always be false), so we don't need to update this place

mkzie2 · 2025-08-24T19:22:41Z

Thanks @DylanDylann, I have updated the code

mkzie2 · 2025-08-25T05:44:44Z

The failed test is due to flaky test which was already mentioned here #68451

DylanDylann · 2025-08-25T08:15:07Z

src/libs/actions/Task.ts

    reports: OnyxCollection<OnyxTypes.Report>,
    personalDetails: OnyxEntry<OnyxTypes.PersonalDetailsList>,
    localeCompare: LocaleContextProps['localeCompare'],
+    isReportArchived = false,


Let's revert this

DylanDylann · 2025-08-25T08:16:03Z

src/pages/ShareCodePage.tsx


        return currentUserPersonalDetails.login;
-    }, [isReport, currentUserPersonalDetails.login, report, isReportArchived]);
+    }, [report, currentUserPersonalDetails, isReport, isReportArchived]);


Why do you update currentUserPersonalDetails.login to currentUserPersonalDetails

Suggested change

}, [report, currentUserPersonalDetails, isReport, isReportArchived]);

}, [report, currentUserPersonalDetails.login, isReport, isReportArchived]);

DylanDylann · 2025-08-25T08:17:37Z

Please update getChatRoomSubtitle call in AvatarWithDisplayName

DylanDylann · 2025-08-25T08:19:42Z

tests/unit/SidebarUtilsTest.ts

                });

-                expect(optionData?.alternateText).toBe(`test message`);
+                expect(optionData?.alternateText).toBe(`One: test message`);


@mkzie2 Why do you change the expect here?

DylanDylann · 2025-08-25T08:21:34Z

tests/unit/ReportUtilsTest.ts

            );

-            expect(title).toBeCalledWith(
+            expect(title).toHaveBeenCalledWith(


Same question?

Ahh It seems, toBeCalledWith is deprecated. Let's ignore this

DylanDylann · 2025-08-25T08:21:39Z

tests/unit/ReportUtilsTest.ts

            );

-            expect(description).toBeCalledWith(
+            expect(description).toHaveBeenCalledWith(


Ahh It seems, toBeCalledWith is deprecated. Let's ignore this

mkzie2 · 2025-08-26T07:45:18Z

Hey @DylanDylann, could you please check the PR again. Thank you

DylanDylann · 2025-08-26T07:53:57Z

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 that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- 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 there are no new alerts related to the canBeMissing param for useOnyx
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 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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- 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.ts 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 UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design 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.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
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.

Screenshots/Videos

Screen.Recording.2025-08-26.at.16.45.22.mov

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

tgolen · 2025-08-26T16:00:27Z

src/libs/OptionsListUtils.ts

    result.isOptimisticPersonalDetail = personalDetail?.isOptimisticPersonalDetail;
    if (report) {
        const reportNameValuePairs = allReportNameValuePairs?.[`${ONYXKEYS.COLLECTION.REPORT_NAME_VALUE_PAIRS}${report.reportID}`];
+        const isReportArchived = isArchivedReport(reportNameValuePairs);


This is the part I hate about the options utils... We already have result.private_isArchived below, which does exactly the same thing. So, for consistency, I like to keep using result.private_isArchived rather than having two variables for the same thing.

I think we should keep doing this until we really want to rename result.private_isArchived to result.isReportArchived, which is a whole lot more work.

I think the best suggestion I have for this is to modify below to change
result.private_isArchived = reportNameValuePairs?.private_isArchived;
to
result.private_isArchived = isReportArchived;

so that they are at least both referencing the same thing.

@tgolen I also think like this

result.private_isArchived = isReportArchived;

But the type is different. And because result.private_isArchived will be outdated, so I suggest we avoid using it. That’s why we introduced the isReportArchived variable here.

I think we should leave this code better than we found it and having duplicate variables only makes the code messier and harder to maintain (because someone might come and change one variable and not see the other).

But the type is different

How so? Is it because one is a boolean and the other is a string (timestamp)? Isn't it easy to update the types? I think we are never really using the string as an actual string, we are always prepending !! to it in order to treat it as a boolean. So, we're already kind of breaking the purpose of the type.

Ideally, we would completely rename result.private_isArchived to result.reportIsArchived. Without a plan to do that, I really don't think we should add this duplicate variable.

result.private_isArchived is still used in many other places. We should handle this in a separate PR by removing all report.private_isArchived usages and replacing them with reportIsArchived.

@mkzie2 In this PR, please update it to continue using private_isArchived in order to avoid duplication

tgolen · 2025-08-26T16:09:08Z

src/libs/ReportUtils.ts

 * Get either the policyName or domainName the chat is tied to
 */
-function getChatRoomSubtitle(report: OnyxEntry<Report>, config: GetChatRoomSubtitleConfig = {isCreateExpenseFlow: false}): string | undefined {
+function getChatRoomSubtitle(report: OnyxEntry<Report>, config: GetChatRoomSubtitleConfig = {isCreateExpenseFlow: false, isReportArchived: false}): string | undefined {


I think this config object is an anti-pattern, so please don't add any more properties to it and add isReportArchived as it's own parameter.

Of course, that leaves the config object with only a single property (hence, why it was an anti-pattern to begin with), so it would be nice for you to also move isCreateExpenseFlow to it's own parameter and change the name to something more appropriate like preferPolicyName. isCreateExpenseFlow makes this method too tightly coupled so it's difficult to reuse.

…ssue/67095

mkzie2 · 2025-08-27T10:01:14Z

@DylanDylann Please help check it one more time. I have updated the PR to address comments

DylanDylann · 2025-08-27T10:07:01Z

src/libs/ReportUtils.ts

 * Get either the policyName or domainName the chat is tied to
 */
-function getChatRoomSubtitle(report: OnyxEntry<Report>, config: GetChatRoomSubtitleConfig = {isCreateExpenseFlow: false}): string | undefined {
+function getChatRoomSubtitle(report: OnyxEntry<Report>, preferPolicyName = false, isReportArchived = false): string | undefined {


Suggested change

function getChatRoomSubtitle(report: OnyxEntry<Report>, preferPolicyName = false, isReportArchived = false): string | undefined {

function getChatRoomSubtitle(report: OnyxEntry<Report>, isPolicyNamePreferred = false, isReportArchived = false): string | undefined {

This is Boolean type

tgolen

That looks great now. Thank you!

tgolen · 2025-08-27T16:10:15Z

tests/unit/ReportUtilsTest.ts

+            expect(result).toBe(policy.name);
+        });
+
+        it('should handle partial config parameter with only isReportArchived', () => {


Some of these descriptions that mention "config parameter" need cleaned up now.

Thanks for the review. I have updated them. Pls help check again @tgolen

OSBotify · 2025-08-28T01:38:57Z

🚀 Deployed to staging by https://github.com/tgolen in version: 9.2.0-0 🚀

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

OSBotify · 2025-09-02T22:17:51Z

🚀 Deployed to production by https://github.com/arosiclair in version: 9.2.0-5 🚀

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

OSBotify · 2025-09-02T23:11:04Z

🚀 Deployed to production by https://github.com/arosiclair in version: 9.2.0-5 🚀

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

feat: refactor getChatRoomSubtitle

e3bf51d

mkzie2 mentioned this pull request Aug 18, 2025

[Due for payment 2025-09-09] Remove call to getReportNameValuePairs() in method getChatRoomSubtitle from ReportUtils.ts #67095

Closed

Merge branch 'main' of https://github.com/Expensify/App into mkzie2-i…

08bf694

…ssue/67095

mkzie2 marked this pull request as ready for review August 19, 2025 18:49

mkzie2 requested a review from a team as a code owner August 19, 2025 18:49

melvin-bot bot requested review from DylanDylann and removed request for a team August 19, 2025 18:49

DylanDylann reviewed Aug 20, 2025

View reviewed changes

mkzie2 added 3 commits August 21, 2025 23:20

feat: merge main

91145ce

fix: prettier

68e19fb

fix: update

7c84ecc

DylanDylann reviewed Aug 22, 2025

View reviewed changes

mkzie2 added 5 commits August 25, 2025 03:03

chore: merge main

b9f187c

fix: comments

12ed04b

fix: comments

84eaf0c

fix: eslint

258c432

fix: new test

b2d00b0

fix: lint

927665b

DylanDylann reviewed Aug 25, 2025

View reviewed changes

mkzie2 added 4 commits August 26, 2025 15:19

chore: merge latest main

c2b8b82

fix: addressed cmt

be22542

fix: addressed cmt

e91eedf

fix: test

32af32c

DylanDylann approved these changes Aug 26, 2025

View reviewed changes

melvin-bot bot requested a review from tgolen August 26, 2025 09:47

tgolen requested changes Aug 26, 2025

View reviewed changes

Merge branch 'main' of https://github.com/Expensify/App into mkzie2-i…

24c32eb

…ssue/67095

DylanDylann mentioned this pull request Aug 27, 2025

Remove call to getReportNameValuePairs() in method canUserPerformWriteAction from ReportUtils.ts part 3 #69144

Merged

51 tasks

chore: addressed new comments

3f5d22a

chore: addressed new comments

4ae23c2

DylanDylann reviewed Aug 27, 2025

View reviewed changes

DylanDylann approved these changes Aug 27, 2025

View reviewed changes

melvin-bot bot requested a review from tgolen August 27, 2025 10:23

fix: naming

7acf941

tgolen requested changes Aug 27, 2025

View reviewed changes

fix: comment

36cb78a

tgolen approved these changes Aug 27, 2025

View reviewed changes

tgolen merged commit 8b30e81 into Expensify:main Aug 27, 2025
22 checks passed

github-actions bot mentioned this pull request Aug 27, 2025

[Due for payment 2025-09-12] Investigate workflow job failing on main: test / test (job 3) #69374

Closed

OSBotify mentioned this pull request Aug 28, 2025

Deploy Checklist: New Expensify 2025-08-28 #69401

Closed

70 tasks

		() => (task?.shareDestination ? getShareDestination(task.shareDestination, reports, personalDetails, localeCompare, isReportArchived) : undefined),
		[task?.shareDestination, reports, personalDetails, localeCompare, isReportArchived],

	}, [report, currentUserPersonalDetails, isReport, isReportArchived]);
	}, [report, currentUserPersonalDetails.login, isReport, isReportArchived]);

	function getChatRoomSubtitle(report: OnyxEntry<Report>, preferPolicyName = false, isReportArchived = false): string \| undefined {
	function getChatRoomSubtitle(report: OnyxEntry<Report>, isPolicyNamePreferred = false, isReportArchived = false): string \| undefined {

Remove call to getReportNameValuePairs() in method getChatRoomSubtitle from ReportUtils.ts #68701

Remove call to getReportNameValuePairs() in method getChatRoomSubtitle from ReportUtils.ts #68701

Uh oh!

Conversation

mkzie2 commented Aug 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Aug 19, 2025

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!

mkzie2 commented Aug 21, 2025

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!

mkzie2 commented Aug 24, 2025

Uh oh!

mkzie2 commented Aug 25, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

DylanDylann commented Aug 25, 2025

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!

mkzie2 commented Aug 26, 2025

Uh oh!

DylanDylann commented Aug 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

tgolen Aug 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

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!

mkzie2 commented Aug 27, 2025

mkzie2 commented Aug 18, 2025 •

edited

Loading

DylanDylann commented Aug 26, 2025 •

edited

Loading

tgolen Aug 26, 2025 •

edited

Loading