Skip to content

Sort join-workspaces by member count and add Show more#86884

Open
MelvinBot wants to merge 9 commits intomainfrom
claude-sortAndLimitJoinWorkspaces
Open

Sort join-workspaces by member count and add Show more#86884
MelvinBot wants to merge 9 commits intomainfrom
claude-sortAndLimitJoinWorkspaces

Conversation

@MelvinBot
Copy link
Copy Markdown
Contributor

Explanation of Change

Updates the /join-workspaces onboarding modal to:

  1. Sort workspaces by member count (descending) — workspaces with the most members now appear first.
  2. Limit visible workspaces to 5 — when there are more than 5 joinable workspaces, only the first 5 are shown initially with a "Show more" button to reveal the rest.

These changes improve the onboarding experience by surfacing the most popular workspaces first and reducing visual clutter when many workspaces are available.

Fixed Issues

$ #86192
PROPOSAL: #86192 (comment)

Tests

  1. Log in with an account that has access to more than 5 joinable workspaces
  2. Navigate to the /join-workspaces onboarding step
  3. Verify workspaces are sorted by member count (highest first)
  4. Verify only the first 5 workspaces are visible
  5. Verify a "Show more" button appears below the list
  6. Click "Show more" and verify all workspaces are now visible
  7. Verify the "Show more" button disappears after clicking it
  8. Verify the "Skip" button remains visible at all times
  9. Log in with an account that has 5 or fewer joinable workspaces
  10. Verify no "Show more" button is shown
  11. Verify all workspaces are displayed and sorted by member count
  • Verify that no errors appear in the JS console

Offline tests

  1. Navigate to the /join-workspaces screen with workspaces loaded
  2. Go offline
  3. Verify the "Show more" button still works (it's purely client-side state)
  4. Verify the "Join now" / "Ask to join" buttons are disabled while offline (existing behavior)

QA Steps

Same as Tests above.

  • 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
  • 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 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
    • 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

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

Sort available workspaces by employee count (descending) so the
largest workspaces appear first. When more than 5 workspaces are
available, show only the first 5 with a "Show more" button to
reveal the rest.

Co-authored-by: Mykhailo <mkhutornyi@users.noreply.github.com>
@codecov
Copy link
Copy Markdown

codecov bot commented Apr 1, 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/CONST/index.ts 93.65% <ø> (ø)
.../OnboardingWorkspaces/BaseOnboardingWorkspaces.tsx 83.33% <77.77%> (-0.54%) ⬇️
... and 17 files with indirect coverage changes

Copy link
Copy Markdown
Contributor

@mkhutornyi mkhutornyi left a comment

Choose a reason for hiding this comment

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

@MelvinBot pull main

<Button
success={false}
large
text={translate('common.skip')}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@MelvinBot The button copy should be "Skip for now"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Updated the button copy to "Skip for now" — added onboarding.skipForNow translation key across all language files.

Comment on lines +197 to +202
<Button
large
text={translate('common.showMore')}
onPress={() => setShowAll(true)}
style={[styles.mt5]}
/>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@MelvinBot This is not button style. See design:

Image

Also, stick to the list content, not at the bottom

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed — changed "Show more" to use the link style (matching the existing pattern in TransactionGroupListExpanded) and moved it from footerContent to listFooterContent so it renders right after the list items inside the scrollable area.

…inWorkspaces

Co-authored-by: {"message":"Not Found","documentation_url":"https://docs.github.com/rest/issues/comments#get-an-issue-comment","status":"404"} <{"message":"Not Found","documentation_url":"https://docs.github.com/rest/issues/comments#get-an-issue-comment","status":"404"}@users.noreply.github.com>

# Conflicts:
#	src/pages/OnboardingWorkspaces/BaseOnboardingWorkspaces.tsx
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Merged main into this branch and resolved a merge conflict in src/pages/OnboardingWorkspaces/BaseOnboardingWorkspaces.tsx. The conflict was between the PR's sort/show-more logic and a change to the translate call signature on main — kept the PR's features with main's translate argument style.

… now

Co-authored-by: Mykhailo <mkhutornyi@users.noreply.github.com>
@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented Apr 7, 2026

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

The diff is too large to include in this comment (62KB), so I've created a gist for you:

📋 View the translation diff here 📋

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply, or directly by running gh gist view --raw 39682424f7523576b8aebd21a3efabe0 | git apply 😉

View workflow run

hasMoreThanFive && !showAll ? (
<View style={[wrapperPadding]}>
<Button
text={translate('common.showMore')}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@MelvinBot this button should be left aligned. And there should be dropdown arrow icon next to the text.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Done — left-aligned the Show more button (via alignItemsStart on the wrapper) and added a down arrow icon next to the text (via iconRight).

@MelvinBot
Copy link
Copy Markdown
Contributor Author

The only failing check is PR Reviewer Checklist — no reviewer has posted their checklist yet. This is not a code issue and doesn't require a fix.

All code checks (tests, ESLint, typecheck, prettier, builds, spellcheck, etc.) are passing. perf-tests is still pending.

Co-authored-by: Mykhailo <mkhutornyi@users.noreply.github.com>
@MelvinBot
Copy link
Copy Markdown
Contributor Author

The only failing check is PR Reviewer Checklist — no reviewer has posted their checklist comment yet. This is not a code issue and doesn't require a fix.

All code checks (ESLint, prettier, spellcheck, builds) are passing. Tests and typecheck are still running.

@MelvinBot
Copy link
Copy Markdown
Contributor Author

The failing test (job 6) is a flaky test unrelated to this PR.

Failing test: tests/unit/MiddlewareTest.ts:146Middleware › HandleUnusedOptimisticID › Request with preexistingReportID

  • Expects global.fetch called 2 times, received 3

Why it's unrelated:

  • This PR only modifies BaseOnboardingWorkspaces.tsx and language files
  • MiddlewareTest.ts is identical to main (zero diff)
  • This same test passes on main's latest CI run

The other failing check (checklist) is the reviewer checklist — not a code issue.

Recommendation: Re-run the failed jobs. This should pass on retry.

Comment on lines +204 to +205
innerStyles={[styles.ph3]}
textStyles={[styles.fontSizeNormal]}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@MelvinBot

Suggested change
innerStyles={[styles.ph3]}
textStyles={[styles.fontSizeNormal]}
shouldShowRightIcon
innerStyles={styles.pl0}

There's still left padding even after applying styles.pl0. It's overridden by padding-left: 16px;. Can you investigate why?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The padding-left: 16px comes from buttonMedium style (src/styles/index.ts:781) which sets paddingHorizontal: 16. React Native Web preprocesses paddingHorizontal into paddingInline, while pl0 uses paddingLeft — styleq sees these as different property keys and applies both CSS classes to the DOM element. The cascade usually resolves correctly (RNW puts paddingLeft in group 3 vs paddingInline in group 2.1), but it's fragile since it depends on internal stylesheet ordering.

Fix: Use innerStyles={styles.ph0} instead of styles.pl0. This overrides with paddingHorizontal: 0, matching the same shorthand level as buttonMedium, so styleq correctly deduplicates them and only one class is applied.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@MelvinBot

Suggested change
innerStyles={[styles.ph3]}
textStyles={[styles.fontSizeNormal]}
shouldShowRightIcon
innerStyles={styles.ph0}

Also, there should be iconRightHoverFill and iconRightFill to match text style.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Done — added shouldShowRightIcon, changed innerStyles to styles.ph0, and added iconRightFill={theme.link} and iconRightHoverFill={theme.linkHover} so the arrow icon matches the link text color.

@MelvinBot
Copy link
Copy Markdown
Contributor Author

🤖 Code Review

Two issues to address:

1. allPolicyIDItems should be memoized

The sort + map runs on every render. Wrap it in useMemo with [joinablePolicies, isOffline, translate, icons.FallbackWorkspaceAvatar] as dependencies — handleJoinWorkspace should also be wrapped in useCallback or the list items will get new rightElement references each render.

2. Magic number 5 should be a named constant

The limit 5 appears in two places (the slice and the hasMoreThanFive check). Extract it to CONST.ts (e.g., CONST.ONBOARDING.JOINABLE_WORKSPACES_LIMIT) so it's documented and easy to change.

Minor / non-blocking
  • useState(false) for showAll is declared at line 104, between hooks and the derived data. Convention is to group all useState calls together near the top of the component (closer to line 40-42 area).
  • The PR description's Screenshots sections are all empty — make sure to add platform screenshots before merging.

@mkhutornyi
Copy link
Copy Markdown
Contributor

mkhutornyi commented Apr 7, 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
web.mov

MelvinBot and others added 2 commits April 7, 2026 15:32
…inWorkspaces

Co-authored-by: Mykhailo <mkhutornyi@users.noreply.github.com>
…m/Expensify/App into claude-sortAndLimitJoinWorkspaces

Co-authored-by: Mykhailo <mkhutornyi@users.noreply.github.com>
@MelvinBot
Copy link
Copy Markdown
Contributor Author

The failing test (MiddlewareTest.ts — "Request with preexistingReportID") is unrelated to this PR's changes. It was fixed on main in #87154, but this branch was behind. I merged main into the branch to pick up that fix.

@MelvinBot
Copy link
Copy Markdown
Contributor Author

⏱️ Ran out of time before I could finish. This usually means the task was too complex or I got stuck exploring. Please try again with a more specific request or post in #melvinbot-ai.

Run details

…and move useState to hook group

Co-authored-by: Mykhailo <mkhutornyi@users.noreply.github.com>
@MelvinBot
Copy link
Copy Markdown
Contributor Author

The only failing checks on this PR are PR Reviewer Checklist, which is an expected checklist reminder — not a real CI failure.

All other checks (ESLint, Prettier, typecheck, tests, builds, CLA, etc.) are either passing or still running. There are no actionable CI failures to fix at this time.

If any of the currently pending checks (tests, typecheck, perf-tests, etc.) fail once they complete, feel free to tag me again and I'll investigate.

@chatgpt-codex-connector
Copy link
Copy Markdown

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

…s' into claude-sortAndLimitJoinWorkspaces

Co-authored-by: Mykhailo <mkhutornyi@users.noreply.github.com>
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Addressed the review feedback from this comment:

  1. allPolicyIDItems memoization — Skipped per mkhutornyi's guidance: React Compiler handles this.
  2. Magic number 5 — Extracted to CONST.ONBOARDING_JOINABLE_WORKSPACES_LIMIT and renamed hasMoreThanFivehasMoreThanLimit.
  3. useState ordering — Moved showAll state declaration up to the hook group near the top of the component.

@mkhutornyi
Copy link
Copy Markdown
Contributor

@MelvinBot mark as ready for review

@MelvinBot MelvinBot marked this pull request as ready for review April 7, 2026 15:41
@MelvinBot MelvinBot requested a review from a team as a code owner April 7, 2026 15:41
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Done — marked this PR as ready for review.

@melvin-bot melvin-bot bot requested review from heyjennahay and mkhutornyi and removed request for a team April 7, 2026 15:42
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Apr 7, 2026

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

@mkhutornyi
Copy link
Copy Markdown
Contributor

@Expensify/design please review

web.mov

(Ignore that only 2 items show. It's because I haven't found test domain which has more than 5 workspaces. It should be 5 items in reality)

@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Apr 7, 2026

We did not find an internal engineer to review this PR, trying to assign a random engineer to #86192 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

@melvin-bot melvin-bot bot requested a review from carlosmiceli April 7, 2026 15:57
@shawnborton
Copy link
Copy Markdown
Contributor

That's looking pretty good to me 👍

@dannymcclain
Copy link
Copy Markdown
Contributor

Looking good to me too 👍

@carlosmiceli
Copy link
Copy Markdown
Contributor

@heyjennahay all yours!

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