Skip to content

Update the transaction thread report loading to show skeleton#65744

Merged
mountiny merged 29 commits intoExpensify:mainfrom
callstack-internal:Update-the-transaction-thread-report-loading-to-show-skeleton
Jul 14, 2025
Merged

Update the transaction thread report loading to show skeleton#65744
mountiny merged 29 commits intoExpensify:mainfrom
callstack-internal:Update-the-transaction-thread-report-loading-to-show-skeleton

Conversation

@rinej
Copy link
Contributor

@rinej rinej commented Jul 9, 2025

Explanation of Change

The PR was copied, because I need the write permission to modify it
Original PR -> #64211

Fixed Issues

$ #63253
PROPOSAL: #63253 (comment)

Tests

  • Open Reports > Expense Reports
  • Open an expense report with multiple transactions on it
  • Open one transaction thread
  • Ensure the transaction details are loaded immediately (since all the transaction data should be available)
  • Use the arrows in the header to cycle through the expense views
  • The transaction details should be visible immediately even if the report actions are loading
Transactions-Web.mp4

Offline tests

QA Steps

  • Same as tests.

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (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
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • 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 followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • 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
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • 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.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user 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.

Screenshots/Videos

Android: Native
Transaction-android.mp4
Android: mWeb Chrome
Transactions-mWebAndroid.mp4
iOS: Native
Transactions-iOS.mp4
iOS: mWeb Safari
Transaction-mWebiOS.mp4
MacOS: Chrome / Safari
Transactions-Web.mp4
MacOS: Desktop
Transaction-Desktop.mov

pac-guerreiro and others added 20 commits June 15, 2025 17:01
…action-thread-report-loading-to-show-skeleton-for-report-actions-only-if-transaction-data-available
…action-thread-report-loading-to-show-skeleton-for-report-actions-only-if-transaction-data-available

# Conflicts:
#	src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx
#	src/components/MoneyRequestReportView/MoneyRequestReportTransactionsNavigation.tsx
#	src/pages/home/ReportScreen.tsx
#	src/pages/home/report/ReportActionsView.tsx
…action-thread-report-loading-to-show-skeleton-for-report-actions-only-if-transaction-data-available

# Conflicts:
#	src/pages/home/ReportScreen.tsx
#	src/pages/home/report/ReportActionsList.tsx
#	src/pages/home/report/ReportActionsView.tsx
…action-thread-report-loading-to-show-skeleton-for-report-actions-only-if-transaction-data-available
…action-thread-report-loading-to-show-skeleton-for-report-actions-only-if-transaction-data-available
…action-thread-report-loading-to-show-skeleton-for-report-actions-only-if-transaction-data-available
…action-thread-report-loading-to-show-skeleton-for-report-actions-only-if-transaction-data-available
…action-thread-report-loading-to-show-skeleton-for-report-actions-only-if-transaction-data-available
@rinej rinej marked this pull request as ready for review July 9, 2025 13:52
@rinej rinej requested a review from a team as a code owner July 9, 2025 13:52
@melvin-bot melvin-bot bot requested review from allgandalf and removed request for a team July 9, 2025 13:52
@melvin-bot
Copy link

melvin-bot bot commented Jul 9, 2025

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

@mountiny mountiny self-requested a review July 9, 2025 14:10
@github-actions
Copy link
Contributor

github-actions bot commented Jul 9, 2025

🚧 @mountiny has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions

This comment has been minimized.

@github-actions
Copy link
Contributor

🚧 @mountiny has triggered a test Expensify/App build. You can view the workflow run here.

const [reportMetadata = defaultReportMetadata] = useOnyx(`${ONYXKEYS.COLLECTION.REPORT_METADATA}${reportIDFromRoute}`, {canBeMissing: true, allowStaleData: true});
const [policies = getEmptyObject<NonNullable<OnyxCollection<OnyxTypes.Policy>>>()] = useOnyx(ONYXKEYS.COLLECTION.POLICY, {allowStaleData: true, canBeMissing: false});
const [parentReportAction] = useOnyx(`${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${getNonEmptyStringOnyxID(reportOnyx?.parentReportID)}`, {
const [policies = getEmptyObject<NonNullable<OnyxCollection<OnyxTypes.Policy>>>()] = useOnyx(ONYXKEYS.COLLECTION.POLICY, {allowStaleData: true, initialValue: {}, canBeMissing: false});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think @VickyStash is in process of removing the initialValue

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it looks like something went wrong during the conflicts resolution. No need in initialValue: {}

Copy link
Contributor Author

@rinej rinej Jul 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes thats right, I will remove it

),
[reportActions, isOffline, canPerformWriteAction, reportTransactionIDs],
isReportTransactionThread
? reportActions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we still want the same logic as this for report transaction thread though:

(isOffline || isDeletedParentAction(reportAction) || reportAction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE || reportAction.errors) &&
                          shouldReportActionBeVisible(reportAction, reportAction.reportActionID, canPerformWriteAction) &&

Why is it removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wasn't in the initial implementation, so had to double check, but I tested and I agree that we do need that filter there. I will revert it. (I think it was initially added for some render optimization, but didn't notice any impact)

const handleDeleteModalConfirm = useCallback(() => {
setIsDeleteModalVisible(false);
if (!parentReportAction || !transaction) {
throw new Error('Data missing');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How will this look like in prod?

// Parse Fullstory attributes on initial render
useLayoutEffect(parseFSAttributes, []);

const ListComponent = isTransactionThread(parentReportAction) ? FlatList : InvertedFlatList;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not understand why we bringing this change here and it was not needed before? Feels quite significant change

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was added to fix the content shifting issue in when switching between transaction reports

Without that change:

Shifting.mp4

With that change:

NoShifting.mp4

I agree that it is the significant change (even though it is only for TransactionThread).

I will revisit it, maybe I will be able to find some better solution to fix it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I compared it with main, the behaviour is similar as on first video, so that shifting is already on main (so the changes on this branch didn't caused it)

Maybe we don't need it or it is not in the scope of this ticket?

@mountiny Let me know your thoughts, I will revert that logic then.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rinej I am not sure about this change right now, could we revert it please?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, understand we don't wont to add to much changes in one PR, I reverted it ✅
If by any change we would like that logic, we can create separate issue for it

@mountiny
Copy link
Contributor

Screen.Recording.2025-07-10.at.16.24.39.mp4

Also noting the receipt flickering, but NAB here

@github-actions
Copy link
Contributor

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪
Built from App PR #65744.

Android 🤖 iOS 🍎
⏩ SKIPPED ⏩ ❌ FAILED ❌
The build for Android was skipped The QR code can't be generated, because the iOS build failed
Desktop 💻 Web 🕸️
⏩ SKIPPED ⏩ https://65744.pr-testing.expensify.com
The build for Desktop was skipped Web

👀 View the workflow run that generated this build 👀

@mountiny
Copy link
Contributor

@allgandalf can you please retest again? thanks

@allgandalf
Copy link
Contributor

I will but jest is failing can we fix that please

@rinej
Copy link
Contributor Author

rinej commented Jul 14, 2025

I'm on it

@rinej
Copy link
Contributor Author

rinej commented Jul 14, 2025

I found some flaky test in ReportUtilsTest.ts, so it is not related to the changes in the PR.

In the ReportUtilsTest.ts

            const report: Report = {
                ...createRandomReport(1),
                type: CONST.REPORT.TYPE.CHAT,
                participants: {
                    ...buildParticipantsFromAccountIDs([currentUserAccountID, 1234]),
                    [currentUserAccountID]: {
                        notificationPreference: CONST.REPORT.NOTIFICATION_PREFERENCE.HIDDEN,
                    },
                },
            };

            await Onyx.set(ONYXKEYS.SESSION, {email: currentUserEmail, accountID: currentUserAccountID});

            expect(canLeaveChat(report, undefined)).toBe(false);
        });
        

We are creating random report and test the canLeaveChat function.

It works well for all of report types, exept when
chatType = policyExpenseChat

When we have that type the logic inside the canLeaveChat returns true and cause the test to fails.

    if (isPolicyExpenseChat(report) && !report?.isOwnPolicyExpenseChat && !isPolicyAdminPolicyUtils(policy)) {
        return true;
    }

The tests where added 5 days ago. The fix is quite easy, just make sure that when we create the random report for tests, do not include policyExpenseChat as the chatType.

@mountiny @allgandalf
Should I fix this test in this PR? Or do in another issue, as it is not related?

@mountiny
Copy link
Contributor

@rinej all good its handled here #66023

Comment on lines +222 to +229
parentReportIDFromRoute && parentReportActionIDFromRoute
? ({
...reportOnyx,
reportID: reportIDFromRoute,
parentReportID: parentReportIDFromRoute,
parentReportActionID: parentReportActionIDFromRoute,
policyID: parentReport?.policyID,
type: CONST.REPORT.TYPE.CHAT,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please leave more comments around this to explain why we do it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done ✅

// Parse Fullstory attributes on initial render
useLayoutEffect(parseFSAttributes, []);

const ListComponent = isTransactionThread(parentReportAction) ? FlatList : InvertedFlatList;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rinej I am not sure about this change right now, could we revert it please?

@pac-guerreiro
Copy link
Contributor

@mountiny, regarding this comment, I made this change so that the list would remain focused at the top. The InvertedList component is made in a way that focus the list on the bottom.

Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @pac-guerreiro @rinej can you please proactively check for new deploy blockers that might be related to this as with the memozation I would imagine there might be some issues popping up

@mountiny mountiny merged commit 6637833 into Expensify:main Jul 14, 2025
22 of 23 checks passed
@OSBotify
Copy link
Contributor

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

@github-actions
Copy link
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 9.1.81-0 🚀

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

@mountiny
Copy link
Contributor

I had to revert this because of https://expensify.slack.com/archives/C05LX9D6E07/p1752552404895209, as the flatlist changes been reverted, we did not retest the transaction thread and system messages been showing above the transaction details

@github-actions
Copy link
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.1.81-7 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants