Skip to content

Fix: Replace InviteMemberListItem with SingleSelectWithAvatarListItem on DomainAddAdminPage#81815

Merged
chuckdries merged 11 commits intoExpensify:mainfrom
PiyushChandra17:fix/80353
Feb 24, 2026
Merged

Fix: Replace InviteMemberListItem with SingleSelectWithAvatarListItem on DomainAddAdminPage#81815
chuckdries merged 11 commits intoExpensify:mainfrom
PiyushChandra17:fix/80353

Conversation

@PiyushChandra17
Copy link
Copy Markdown
Contributor

Explanation of Change

Replace InviteMemberListItem with SingleSelectWithAvatarListItem on DomainAddAdminPage

Fixed Issues

$ #80353
PROPOSAL: #80353(Comment)

Tests

  • Precondition: WS has Domain name added && Login via email as their domain name
  1. Open the New Expensify App
  2. Click on "Workspaces" tab > Go to "Domain admins"
  3. Click on "Add admin"
  4. On DomainAddAdminPage > Verify the selected contact now has newly introduced Single Select List Item styles with Avatars and hovering over the item, the row gets a Background Highlight
  • Verify that no errors appear in the JS console

Offline tests

Same as tests

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

Android: Native
Android: mWeb Chrome android-mweb-chrome-fix-singleselectwithavatar
iOS: Native
iOS: mWeb Safari ios-mweb-safari-fix-singleselectwithavatar
MacOS: Chrome / Safari macos-chrome-fix-single-select-list-with-avatar

@PiyushChandra17 PiyushChandra17 requested review from a team as code owners February 9, 2026 04:54
@melvin-bot melvin-bot Bot requested review from Ollyws and heyjennahay and removed request for a team February 9, 2026 04:54
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Feb 9, 2026

@Ollyws 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 February 9, 2026 04:54
return (
<Checkbox
shouldSelectOnPressEnter
containerBorderRadius={999}
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.

❌ CONSISTENCY-2 (docs)

The value 999 is a magic number without documentation. This border radius value should be defined as a named constant to improve code readability and maintainability.

Suggested fix:

const CIRCULAR_BORDER_RADIUS = 999; // Large value to create circular border

const radioCheckboxComponent = useCallback(() => {
    return (
        <Checkbox
            shouldSelectOnPressEnter
            containerBorderRadius={CIRCULAR_BORDER_RADIUS}
            accessibilityLabel="SingleSelectListItem"
            isChecked={isSelected}
            onPress={() => onSelectRow(item)}
        />
    );
}, [isSelected, item, onSelectRow]);

Or better yet, if this value is used elsewhere in the codebase, it should be defined in a shared constants file.


Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

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.

Agreed, can you please add a style constant somewhere for circular/full border radius?

@codecov
Copy link
Copy Markdown

codecov Bot commented Feb 9, 2026

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/pages/domain/Admins/DomainAddAdminPage.tsx 0.00% <ø> (ø)
...istWithSections/SingleSelectWithAvatarListItem.tsx 0.00% <0.00%> (ø)
... and 21 files with indirect coverage changes

@PiyushChandra17
Copy link
Copy Markdown
Contributor Author

@shawnborton Does the Avatar size looks correct here?

avatar_size

cc @dannymcclain @dubielzyk-expensify

@shawnborton
Copy link
Copy Markdown
Contributor

Hmm I would think each of these rows would be 64px tall (12px vertical padding + 40px avatar = 64px), basically can we reuse our standard row pattern we have elsewhere for displaying avatar + names?
CleanShot 2026-02-10 at 11 07 30@2x

@PiyushChandra17
Copy link
Copy Markdown
Contributor Author

I would think each of these rows would be 64px tall (12px vertical padding + 40px avatar = 64px)

@shawnborton Perhaps we need to use existing styles.optionRow (64px tall) whereas styles.compactRow is 52px ....

can we reuse our standard row pattern we have elsewhere for displaying avatar + names?

Yeah that does make sense, i have looked into this , all the MultiSelect List Items uses 52x40 > Avatar size ....

PS: Will update the PR first time at the desk tomm. if that works OR most probably get this done today itself.

@shawnborton
Copy link
Copy Markdown
Contributor

Okay keep us posted!

@PiyushChandra17
Copy link
Copy Markdown
Contributor Author

Cool ....

@PiyushChandra17
Copy link
Copy Markdown
Contributor Author

@shawnborton Update: Added padding vertical > pv3 > 12px && minHeight > 64px tall > Matches with staging/prod

fix-pv-mh

Here's the Avatar size > 52x40 > matches with staging/prod

52x40

I think this looks correct to me, wdyt?

cc @dannymcclain @dubielzyk-expensify

@shawnborton
Copy link
Copy Markdown
Contributor

I do think that looks correct as well, thanks! Let's see if the others have thoughts too.

@PiyushChandra17
Copy link
Copy Markdown
Contributor Author

I think i have played with this and all the Multi-Select List Items styles in our Expensify/App, perhaps i am kinda pretty sure it's correct though. However let's see what are their thoughts on this. Thanks!

@PiyushChandra17
Copy link
Copy Markdown
Contributor Author

@Ollyws Bump for the review here. Thanks!

@dannymcclain
Copy link
Copy Markdown
Contributor

Looks good to me 👍

@Ollyws
Copy link
Copy Markdown
Contributor

Ollyws commented Feb 17, 2026

@PiyushChandra17 The lint and TS checks are failing.

@PiyushChandra17
Copy link
Copy Markdown
Contributor Author

@Ollyws Yep, this has picked up merge-conflicts lately. Will resolve this ....

@PiyushChandra17
Copy link
Copy Markdown
Contributor Author

@Ollyws Resolved the failing Lint && TS checks ✅

@PiyushChandra17
Copy link
Copy Markdown
Contributor Author

@Ollyws Bump

@Ollyws
Copy link
Copy Markdown
Contributor

Ollyws commented Feb 23, 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
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that 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_Native
Android: mWeb Chrome Android_Chrome
iOS: HybridApp iOS_Native
iOS: mWeb Safari iOS_Safari
MacOS: Chrome / Safari MacOS_Chrome

Copy link
Copy Markdown
Contributor

@Ollyws Ollyws left a comment

Choose a reason for hiding this comment

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

Melvin's comment https://github.com/Expensify/App/pull/81815/changes#r2780590122 does make sense, but other than that LGTM.

@melvin-bot melvin-bot Bot requested a review from chuckdries February 23, 2026 14:38
Copy link
Copy Markdown
Contributor

@chuckdries chuckdries left a comment

Choose a reason for hiding this comment

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

Looks great! Just a small nit

return (
<Checkbox
shouldSelectOnPressEnter
containerBorderRadius={999}
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.

Agreed, can you please add a style constant somewhere for circular/full border radius?

chuckdries
chuckdries previously approved these changes Feb 24, 2026
Copy link
Copy Markdown
Contributor

@chuckdries chuckdries left a comment

Choose a reason for hiding this comment

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

Excellent, thank you

@chuckdries
Copy link
Copy Markdown
Contributor

Hm, looks like we're failing prettier and lint checks. Can you merge main and try to run the checks locally?

@PiyushChandra17
Copy link
Copy Markdown
Contributor Author

@chuckdries Yeah seems like the prettier check is failing even after merge main 🤔 . Looking into this ...

@chuckdries
Copy link
Copy Markdown
Contributor

@PiyushChandra17 I just realized I was misinterpreting the stuff going on in the open source channel. It does appear to be broken in main in CI (but not on my laptop????). Looking into it as well

@PiyushChandra17
Copy link
Copy Markdown
Contributor Author

Agree, i think it's broken in the main CI .. Perhaps let's wait to get this fixed .. And merge latest main and get this going ✅

@PiyushChandra17
Copy link
Copy Markdown
Contributor Author

@chuckdries Ran npm run prettier after merge main and it worked. It's ready for merge ✅

@chuckdries chuckdries merged commit 3741422 into Expensify:main Feb 24, 2026
30 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

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

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/chuckdries in version: 9.3.26-0 🚀

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

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/puneetlath in version: 9.3.26-8 🚀

platform result
🕸 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.

6 participants