Improve import member success message #57726

bernhardoj · 2025-03-04T08:14:26Z

Explanation of Change

Fixed Issues

$ #56941
PROPOSAL: #56941 (comment)

Tests

Same as QA Steps

Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

Open a workspace members page
Import a member spreadsheet that contains new member
When success, verify the message is "X member has/have been added."
Import the same spreadsheet
When success, verify the message is "No members have been added or updated."
Import a member spreadsheet that contains the same member from step 2, but with a different role
When success, verify the message is "X member has/have been updated."
Import a member spreadsheet that contains the same member from step 2, but with a different role and also a new member
When success, verify the message is "X member(s) added, Y member(s) updated"

Spreadsheet:
member add.csv
member update and add.csv
member update.csv

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

android.mp4

Android: mWeb Chrome

android.mweb.mp4

iOS: Native

ios.mp4

iOS: mWeb Safari

ios.mweb.mp4

MacOS: Chrome / Safari

web.mp4

MacOS: Desktop

desktop.mp4

melvin-bot · 2025-03-04T08:14:31Z

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

alitoshmatov · 2025-03-06T22:12:55Z

@bernhardoj Tests are failing

bernhardoj · 2025-03-07T04:24:50Z

It looks unrelated. Merged with main.

bernhardoj · 2025-03-07T04:56:58Z

Hmm, ok, the other test is from ours.

bernhardoj · 2025-03-07T15:02:42Z

Fixed

alitoshmatov · 2025-03-12T02:38:16Z

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 tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- 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 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: Native

import-android.mov

Android: mWeb Chrome

import-mweb.mov

iOS: Native

import-ios.mp4

iOS: mWeb Safari

import-safari.mp4

MacOS: Chrome / Safari

import-web.mov

MacOS: Desktop

import-desktop.mov

alitoshmatov · 2025-03-12T02:38:25Z

LGTM!

bernhardoj · 2025-03-12T03:56:59Z

FYI, the translations are not verified yet on slack: https://expensify.slack.com/archives/C01GTK53T8Q/p1741075110505229

alitoshmatov · 2025-03-21T01:46:49Z

Translations have been approved.

OSBotify · 2025-03-21T04:13:10Z

✋ 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 · 2025-03-21T22:44:07Z

🚀 Deployed to staging by https://github.com/jasperhuangg in version: 9.1.17-0 🚀

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

github-actions · 2025-03-24T21:14:36Z

🚀 Deployed to production by https://github.com/cristipaval in version: 9.1.17-1 🚀

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

improve import member success message

6d78a17

bernhardoj requested a review from a team as a code owner March 4, 2025 08:14

melvin-bot bot requested review from alitoshmatov and removed request for a team March 4, 2025 08:14

bernhardoj added 4 commits March 4, 2025 16:39

lint

d9b1ee9

add test

2d7bf07

add comment

fefb900

disconnect connection

28f5cc2

Merge branch 'main' into fix/56941-improve-import-success-message

7be51a5

prettier

e339d33

fix mock fetch is never resumed

9ea4d33

alitoshmatov approved these changes Mar 21, 2025

View reviewed changes

melvin-bot bot requested a review from jasperhuangg March 21, 2025 01:47

jasperhuangg approved these changes Mar 21, 2025

View reviewed changes

jasperhuangg merged commit eef6093 into Expensify:main Mar 21, 2025
17 checks passed

github-actions bot mentioned this pull request Mar 21, 2025

Deploy Checklist: New Expensify 2025-03-21 #58928

Closed

65 tasks

melvin-bot bot mentioned this pull request Mar 24, 2025

[Due for payment 2025-03-31] [$250] Workspace - Incorrect members number when import spreadsheet #56941

Closed

8 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Improve import member success message #57726

Improve import member success message #57726

Uh oh!

bernhardoj commented Mar 4, 2025 •

edited

Loading

Uh oh!

melvin-bot bot commented Mar 4, 2025

Uh oh!

alitoshmatov commented Mar 6, 2025

Uh oh!

bernhardoj commented Mar 7, 2025

Uh oh!

bernhardoj commented Mar 7, 2025

Uh oh!

bernhardoj commented Mar 7, 2025

Uh oh!

alitoshmatov commented Mar 12, 2025

Uh oh!

alitoshmatov commented Mar 12, 2025

Uh oh!

bernhardoj commented Mar 12, 2025

Uh oh!

alitoshmatov commented Mar 21, 2025

Uh oh!

Uh oh!

OSBotify commented Mar 21, 2025

Uh oh!

github-actions bot commented Mar 21, 2025

Uh oh!

github-actions bot commented Mar 24, 2025

Uh oh!

Uh oh!

Improve import member success message #57726

Improve import member success message #57726

Uh oh!

Conversation

bernhardoj commented Mar 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Mar 4, 2025

Uh oh!

alitoshmatov commented Mar 6, 2025

Uh oh!

bernhardoj commented Mar 7, 2025

Uh oh!

bernhardoj commented Mar 7, 2025

Uh oh!

bernhardoj commented Mar 7, 2025

Uh oh!

alitoshmatov commented Mar 12, 2025

Reviewer Checklist

Screenshots/Videos

Uh oh!

alitoshmatov commented Mar 12, 2025

Uh oh!

bernhardoj commented Mar 12, 2025

Uh oh!

alitoshmatov commented Mar 21, 2025

Uh oh!

Uh oh!

OSBotify commented Mar 21, 2025

Uh oh!

github-actions bot commented Mar 21, 2025

Uh oh!

github-actions bot commented Mar 24, 2025

Uh oh!

Uh oh!

bernhardoj commented Mar 4, 2025 •

edited

Loading