Skip to content

Make loading state for opensearchpage more accurate#85952

Merged
luacmartins merged 5 commits intomainfrom
jsenyitko-optimize-opensearc-skeleton
Mar 20, 2026
Merged

Make loading state for opensearchpage more accurate#85952
luacmartins merged 5 commits intomainfrom
jsenyitko-optimize-opensearc-skeleton

Conversation

@JS00001
Copy link
Contributor

@JS00001 JS00001 commented Mar 20, 2026

Explanation of Change

QOL change. Lets make the loading state for 'OpenSearchPage' more accurate. We previously used a hacky policy?.employeeList !== undefined && policy?.exporter !== undefined); (Since exporter was only returned in opensearchpage), but lets just add a key to track this

Fixed Issues

N/A

Tests

Clear your cache
Open the search page
Ensure a loading skeleton shows up for the suggested searches
Refresh the page or navigate away and back
Ensure the skeleton doesnt show up again

  • Verify that no errors appear in the JS console

Offline tests

Ensure that the skeleton doesnt permanently block the screen in offline mode

QA Steps

Same as tests

  • Verify that no errors appear in the JS console

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 new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • 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

Screen.Recording.2026-03-20.at.10.01.04.AM.mov

@JS00001 JS00001 requested a review from luacmartins March 20, 2026 14:02
@JS00001 JS00001 self-assigned this Mar 20, 2026
@JS00001 JS00001 requested review from a team as code owners March 20, 2026 14:02
@melvin-bot melvin-bot bot requested review from JmillsExpensify and srikarparsi and removed request for a team March 20, 2026 14:02
@melvin-bot
Copy link

melvin-bot bot commented Mar 20, 2026

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

@melvin-bot melvin-bot bot removed the request for review from a team March 20, 2026 14:02
Copy link
Contributor

@JmillsExpensify JmillsExpensify left a comment

Choose a reason for hiding this comment

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

No product review required.

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9e8ca63a9a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@codecov
Copy link

codecov bot commented Mar 20, 2026

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/ONYXKEYS.ts 100.00% <ø> (ø)
src/hooks/useSearchTypeMenuSections.ts 93.10% <ø> (-0.84%) ⬇️
src/libs/actions/Search.ts 28.57% <100.00%> (+0.13%) ⬆️
src/pages/Search/SearchTypeMenu.tsx 0.00% <0.00%> (ø)
... and 31 files with indirect coverage changes

@luacmartins
Copy link
Contributor

@JS00001 we should get a C+ to review/test this PR too

@JS00001 JS00001 requested a review from aimane-chnaif March 20, 2026 17:56
Copy link
Contributor

@aimane-chnaif aimane-chnaif left a comment

Choose a reason for hiding this comment

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

Any reason for removing unit test?

@aimane-chnaif
Copy link
Contributor

aimane-chnaif commented Mar 20, 2026

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

Android: HybridApp
Android: mWeb Chrome
iOS: HybridApp
ios.mov
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-03-20.at.7.38.02.pm.mov
Screen.Recording.2026-03-20.at.7.39.09.pm.mov
offline.mov

@JS00001
Copy link
Contributor Author

JS00001 commented Mar 20, 2026

Any reason for removing unit test?

It tested only the method we removed

@aimane-chnaif
Copy link
Contributor

Any reason for removing unit test?

It tested only the method we removed

yes, but offline case is still valid. We generally add unit tests for hooks.

Let's see what AI suggests.

@MelvinBot please suggest code changes for adding unit tests of useSearchTypeMenuSections hook.

@MelvinBot
Copy link
Contributor

Here's a suggested unit test file for the useSearchTypeMenuSections hook. It follows the existing mock-based pattern (like useSearchShouldCalculateTotals.test.ts) and covers the hook's current API — typeMenuSections and activeItemIndex — including the offline case:

// tests/unit/hooks/useSearchTypeMenuSections.test.ts
/* eslint-disable @typescript-eslint/naming-convention */
import {renderHook} from '@testing-library/react-native';
import useNetwork from '@hooks/useNetwork';
import useSearchTypeMenuSections from '@hooks/useSearchTypeMenuSections';
import CONST from '@src/CONST';
import ONYXKEYS from '@src/ONYXKEYS';

jest.mock('@libs/ReportUtils', () => ({
    getPersonalDetailsForAccountID: jest.fn(),
    hasEmptyReportsForPolicy: jest.fn(() => false),
    hasViolations: jest.fn(() => false),
}));

jest.mock('@userActions/Report', () => ({
    createNewReport: jest.fn(() => ({reportID: 'mock-report-id'})),
}));

jest.mock('@hooks/useCardFeedsForDisplay', () => jest.fn(() => ({defaultCardFeed: null, cardFeedsByPolicy: {}})));
jest.mock('@hooks/useCreateEmptyReportConfirmation', () => jest.fn(() => ({openCreateReportConfirmation: jest.fn()})));
jest.mock('@hooks/useNetwork', () => jest.fn(() => ({isOffline: false})));
jest.mock('@hooks/usePermissions', () => jest.fn(() => ({isBetaEnabled: jest.fn(() => false)})));

const onyxData: Record<string, unknown> = {};

const mockUseOnyx = jest.fn(
    (
        key: string,
        options?: {
            selector?: (value: unknown) => unknown;
        },
    ) => {
        const value = onyxData[key];
        const selectedValue = options?.selector ? options.selector(value as never) : value;
        return [selectedValue];
    },
);

jest.mock('@hooks/useOnyx', () => ({
    __esModule: true,
    default: (key: string, options?: {selector?: (value: unknown) => unknown}) => mockUseOnyx(key, options),
}));

const mockUseMappedPolicies = jest.fn(() => [onyxData[ONYXKEYS.COLLECTION.POLICY], {}]);

jest.mock('@hooks/useMappedPolicies', () => ({
    __esModule: true,
    default: () => mockUseMappedPolicies(),
}));

describe('useSearchTypeMenuSections', () => {
    beforeEach(() => {
        onyxData[ONYXKEYS.COLLECTION.POLICY] = {};
        onyxData[ONYXKEYS.SESSION] = {email: 'test@example.com', accountID: 1};
        onyxData[ONYXKEYS.SAVED_SEARCHES] = {};
        onyxData[ONYXKEYS.COLLECTION.REPORT] = {};

        (useNetwork as jest.Mock).mockReturnValue({isOffline: false});
        mockUseOnyx.mockClear();
    });

    it('returns typeMenuSections with at least the Explore section', () => {
        const {result} = renderHook(() => useSearchTypeMenuSections());

        expect(result.current.typeMenuSections.length).toBeGreaterThanOrEqual(1);

        const exploreSection = result.current.typeMenuSections.find((s) => s.translationPath === 'common.explore');
        expect(exploreSection).toBeDefined();
        expect(exploreSection?.menuItems.length).toBeGreaterThanOrEqual(1);
    });

    it('returns activeItemIndex of -1 when hash matches a saved search', () => {
        onyxData[ONYXKEYS.SAVED_SEARCHES] = {
            12345: {name: 'My saved search', query: 'type:expense'},
        };

        const {result} = renderHook(() => useSearchTypeMenuSections({hash: 12345}));

        expect(result.current.activeItemIndex).toBe(-1);
    });

    it('returns activeItemIndex of -1 when no similarSearchHash matches any item', () => {
        const {result} = renderHook(() => useSearchTypeMenuSections({similarSearchHash: 99999}));

        expect(result.current.activeItemIndex).toBe(-1);
    });

    it('returns correct activeItemIndex when similarSearchHash matches an item', () => {
        const {result} = renderHook(() => useSearchTypeMenuSections());

        // Get the first item's similarSearchHash from the generated sections
        const firstItem = result.current.typeMenuSections[0]?.menuItems[0];
        expect(firstItem).toBeDefined();

        const {result: resultWithMatch} = renderHook(() => useSearchTypeMenuSections({similarSearchHash: firstItem.similarSearchHash}));

        expect(resultWithMatch.current.activeItemIndex).toBe(0);
    });

    it('returns correct flattened activeItemIndex for items in later sections', () => {
        // Set up a policy that enables multiple sections (Todo section needs a paid group policy)
        onyxData[ONYXKEYS.COLLECTION.POLICY] = {
            policy1: {
                id: 'policy1',
                type: 'team',
                role: 'admin',
                owner: 'test@example.com',
                employeeList: {'test@example.com': {accountID: 1, submitsTo: 'test@example.com'}},
                exporter: 'test@example.com',
                approver: 'test@example.com',
                approvalMode: 'basic',
                isPolicyExpenseChatEnabled: true,
                reimbursementChoice: 'reimburseManual',
            },
        };

        const {result} = renderHook(() => useSearchTypeMenuSections());

        // If we have multiple sections, find an item in the second section
        if (result.current.typeMenuSections.length > 1) {
            const firstSectionLength = result.current.typeMenuSections[0].menuItems.length;
            const secondSectionFirstItem = result.current.typeMenuSections[1]?.menuItems[0];

            if (secondSectionFirstItem) {
                const {result: resultWithMatch} = renderHook(() =>
                    useSearchTypeMenuSections({similarSearchHash: secondSectionFirstItem.similarSearchHash}),
                );

                expect(resultWithMatch.current.activeItemIndex).toBe(firstSectionLength);
            }
        }
    });

    it('shows saved searches section when saved searches exist', () => {
        onyxData[ONYXKEYS.SAVED_SEARCHES] = {
            12345: {name: 'My saved search', query: 'type:expense'},
        };

        const {result} = renderHook(() => useSearchTypeMenuSections());

        const savedSection = result.current.typeMenuSections.find((s) => s.translationPath === 'search.savedSearchesMenuItemTitle');
        expect(savedSection).toBeDefined();
    });

    it('includes optimistically deleted saved searches when offline', () => {
        (useNetwork as jest.Mock).mockReturnValue({isOffline: true});

        onyxData[ONYXKEYS.SAVED_SEARCHES] = {
            12345: {
                name: 'Deleted search',
                query: 'type:expense',
                pendingAction: CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE,
            },
        };

        const {result} = renderHook(() => useSearchTypeMenuSections());

        const savedSection = result.current.typeMenuSections.find((s) => s.translationPath === 'search.savedSearchesMenuItemTitle');
        expect(savedSection).toBeDefined();
    });

    it('excludes optimistically deleted saved searches when online', () => {
        (useNetwork as jest.Mock).mockReturnValue({isOffline: false});

        onyxData[ONYXKEYS.SAVED_SEARCHES] = {
            12345: {
                name: 'Deleted search',
                query: 'type:expense',
                pendingAction: CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE,
            },
        };

        const {result} = renderHook(() => useSearchTypeMenuSections());

        const savedSection = result.current.typeMenuSections.find((s) => s.translationPath === 'search.savedSearchesMenuItemTitle');
        expect(savedSection).toBeUndefined();
    });
});

What's covered

Test What it validates
Explore section always present typeMenuSections contains at least the Explore section with REPORTS/EXPENSES/CHATS
Saved search hash → activeItemIndex -1 When hash matches a saved search key, the hook correctly returns -1 (saved search is active, not a suggested search)
No match → activeItemIndex -1 When similarSearchHash doesn't match any item
Match in first section → index 0 activeItemIndex correctly identifies the matched item
Match in later section → flattened index activeItemIndex correctly accounts for section offsets
Saved searches section visibility Shows when saved searches exist
Offline: deleted saved searches visible Saved searches with pendingAction: DELETE remain visible offline
Online: deleted saved searches hidden Saved searches with pendingAction: DELETE are filtered out online

The last two tests cover the offline case the reviewer mentioned — the isOffline flag affects whether optimistically-deleted saved searches are shown in the menu sections.

@aimane-chnaif
Copy link
Contributor

Please add above tests if applicable

@melvin-bot melvin-bot bot requested a review from MarioExpensify March 20, 2026 19:46
@melvin-bot
Copy link

melvin-bot bot commented Mar 20, 2026

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

@melvin-bot
Copy link

melvin-bot bot commented Mar 20, 2026

🎯 @aimane-chnaif, thanks for reviewing and testing this PR! 🎉

An E/App issue has been created to issue payment here: #85987.

@MelvinBot
Copy link
Contributor

🔍 PR Review

Overall: The approach is sound — replacing the hacky employeeList !== undefined && exporter !== undefined heuristic with an explicit IS_SEARCH_PAGE_DATA_LOADED flag set on API success is cleaner and more reliable.

What looks good

  • The isLoadingOnyxValue(isSearchDataLoadedResult) guard in SearchTypeMenu.tsx:94 is a nice touch — it prevents a skeleton flash while Onyx hydrates the key from storage on app restart.
  • The key is correctly not in KEYS_TO_PRESERVE, so it resets on sign-out/Onyx.clear(). Users will see the skeleton on their first load after login, which is the right behavior.

Items to consider

  1. Test coverage — As discussed in the thread, unit tests for the hook's remaining behavior (typeMenuSections composition, activeItemIndex logic, offline behavior affecting saved search visibility) should be added back. See my earlier suggestion for a concrete test file.

  2. canBeMissing on the new useOnyx callSearchTypeMenu.tsx:57 calls useOnyx(ONYXKEYS.IS_SEARCH_PAGE_DATA_LOADED) without canBeMissing. Since this key starts as undefined (no default value, no init call), it may need canBeMissing: true depending on the current validation rules. The PR author's checklist confirms they checked this, so likely fine — just flagging it.

  3. Behavioral change with persistence — Worth noting: the old heuristic evaluated data freshness on every render (checking if employeeList/exporter were populated), so the skeleton showed on every cold start until OpenSearchPage returned. The new flag persists in Onyx, so after the first successful load, the skeleton won't show on subsequent app restarts (data is already in Onyx cache). This is arguably better UX, but it's a subtle behavioral shift from the old approach.

@luacmartins luacmartins merged commit 72baaed into main Mar 20, 2026
31 of 34 checks passed
@luacmartins luacmartins deleted the jsenyitko-optimize-opensearc-skeleton branch March 20, 2026 19:52
@github-actions
Copy link
Contributor

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

@chatgpt-codex-connector
Copy link

Codex Review: Didn't find any major issues. Breezy!

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@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.

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.3.42-0 🚀

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

Bundle Size Analysis (Sentry):

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.

6 participants