Fix/27776 Workspace - WS invite page keeps loading in offline if no members present #28897

DylanDylann · 2023-10-05T08:54:58Z

Details

Workspace - WS invite page keeps loading in offline if no members present

Fixed Issues

$ #27776
PROPOSAL: #27776 (comment)

Tests

Logout
Login again
Click profile
Click preferences
Toggle on forced offline
Navigate to LHN
Click profile icon
Click workspaces and choose a workspace
Verify that members are not displayed and have text 'You must be online in order to view members of this workspace'

Verify that no errors appear in the JS console

Offline tests

QA Steps

Logout
Login again
Click profile
Click preferences
Toggle on forced offline
Navigate to LHN
Click profile icon
Click workspaces and choose a workspace
Verify that members are not displayed and have text 'You must be online in order to view members of this workspace'

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 / Chrome
- iOS / native
- iOS / 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 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- 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 verified the translation was requested/reviewed 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
- 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.js 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 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
- If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
- 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(themeColors.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 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.
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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

web.mov

Mobile Web - Chrome

chrome.mp4

Mobile Web - Safari

safari.mp4

Desktop

desktop.mov

iOS

ios.mov

Android

android.mov

melvin-bot · 2023-10-05T09:15:05Z

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

robertKozik · 2023-10-05T12:09:11Z

@DylanDylann I saw that there is no link to slack conversation about the Spanish translation. Do we get a proper copy and translation for this issue/PR?

DylanDylann · 2023-10-05T13:11:24Z

@robertKozik I ask about Spanish copy here

robertKozik · 2023-10-05T14:08:50Z

If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

Could you request on the #expensify-open-source as well?

DylanDylann · 2023-10-09T16:25:05Z

@robertKozik We are waiting for a copy translation. But could you help to review the logic of this PR first?

robertKozik · 2023-10-09T21:05:40Z

Already did it. I'll post the reviewer checklist for confirmation in a sec

robertKozik · 2023-10-09T21:14:08Z

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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
- 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.js 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(themeColors.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 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.
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

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

src/languages/en.ts

src/languages/es.ts

MariaHCD · 2023-10-10T07:20:26Z

src/pages/workspace/WorkspaceMembersPage.js

-    const headerMessage = searchValue.trim() && !data.length ? props.translate('workspace.common.memberNotFound') : '';
+
+    const getHeaderMessage = () => {
+        if (isOfflineAndNeedGetData) {


Maybe this variable can be named a bit clearer. How about:

Suggested change

if (isOfflineAndNeedGetData) {

if (isOfflineAndNoMemberDataAvailable) {

@MariaHCD Thanks for your comment, i just updated code. Please check again

cc @robertKozik

Co-authored-by: Maria D'Costa <mariahcdcosta@gmail.com>

MariaHCD

LGTM! We should we good to go once the reviewer checklist is complete, @robertKozik

robertKozik

LGTM! checklist completed 🚀

OSBotify · 2023-10-10T15:36:43Z

✋ 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 · 2023-10-11T05:08:38Z

🚀 Deployed to staging by https://github.com/MariaHCD in version: 1.3.81-0 🚀

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

OSBotify · 2023-10-12T04:50:05Z

🚀 Deployed to staging by https://github.com/MariaHCD in version: 1.3.83-0 🚀

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

DylanDylann added 2 commits October 5, 2023 15:45

fix: in offline mode not show workspace member

165479f

fix lint

1b75c22

DylanDylann changed the title ~~fix: in offline mode not show workspace member~~ fix/27776 Workspace - WS invite page keeps loading in offline if no members present Oct 5, 2023

DylanDylann changed the title ~~fix/27776 Workspace - WS invite page keeps loading in offline if no members present~~ Fix/27776 Workspace - WS invite page keeps loading in offline if no members present Oct 5, 2023

DylanDylann marked this pull request as ready for review October 5, 2023 09:15

DylanDylann requested a review from a team as a code owner October 5, 2023 09:15

melvin-bot bot requested review from robertKozik and removed request for a team October 5, 2023 09:15

DylanDylann mentioned this pull request Oct 5, 2023

[HOLD for payment 2023-10-23] [HOLD for payment 2023-10-23] [HOLD for payment 2023-10-20] [HOLD for payment 2023-10-20] [$500] Workspace - WS invite page keeps loading in offline if no members present #27776

Closed

6 tasks

MariaHCD requested changes Oct 10, 2023

View reviewed changes

DylanDylann and others added 3 commits October 10, 2023 15:01

Update en.ts

b0c8503

Co-authored-by: Maria D'Costa <mariahcdcosta@gmail.com>

Update es.ts

6f9cbbc

Co-authored-by: Maria D'Costa <mariahcdcosta@gmail.com>

Name variable clearer in workspace member page

eba4c5d

MariaHCD approved these changes Oct 10, 2023

View reviewed changes

robertKozik approved these changes Oct 10, 2023

View reviewed changes

melvin-bot bot requested a review from MariaHCD October 10, 2023 14:08

MariaHCD approved these changes Oct 10, 2023

View reviewed changes

MariaHCD merged commit c68bf6a into Expensify:main Oct 10, 2023

OSBotify mentioned this pull request Oct 11, 2023

Deploy Checklist: New Expensify 2023-10-11 #29252

Closed

OSBotify mentioned this pull request Oct 12, 2023

Deploy Checklist: New Expensify 2023-10-12 #29417

Closed

97 tasks

idanbe4 mentioned this pull request May 17, 2024

[Snyk] Security upgrade expo from 50.0.4 to 51.0.8 be4solutions/App#10

Open

MelvinBot mentioned this pull request May 17, 2024

[Snyk] Security upgrade expo from 50.0.4 to 51.0.8 #42357

Closed

50 tasks

melvin-bot bot mentioned this pull request May 17, 2024

[Snyk] Security upgrade expo from 50.0.4 to 51.0.8 #42358

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix/27776 Workspace - WS invite page keeps loading in offline if no members present #28897

Fix/27776 Workspace - WS invite page keeps loading in offline if no members present #28897

DylanDylann commented Oct 5, 2023 •

edited

Loading

melvin-bot bot commented Oct 5, 2023

robertKozik commented Oct 5, 2023

DylanDylann commented Oct 5, 2023

robertKozik commented Oct 5, 2023

DylanDylann commented Oct 9, 2023

robertKozik commented Oct 9, 2023

robertKozik commented Oct 9, 2023 •

edited

Loading

MariaHCD Oct 10, 2023

DylanDylann Oct 10, 2023 •

edited

Loading

MariaHCD left a comment

robertKozik left a comment

OSBotify commented Oct 10, 2023

OSBotify commented Oct 11, 2023

OSBotify commented Oct 12, 2023

	if (isOfflineAndNeedGetData) {
	if (isOfflineAndNoMemberDataAvailable) {

Fix/27776 Workspace - WS invite page keeps loading in offline if no members present #28897

Fix/27776 Workspace - WS invite page keeps loading in offline if no members present #28897

Conversation

DylanDylann commented Oct 5, 2023 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Oct 5, 2023

robertKozik commented Oct 5, 2023

DylanDylann commented Oct 5, 2023

robertKozik commented Oct 5, 2023

DylanDylann commented Oct 9, 2023

robertKozik commented Oct 9, 2023

robertKozik commented Oct 9, 2023 • edited Loading

Reviewer Checklist

Screenshots/Videos

MariaHCD Oct 10, 2023

Choose a reason for hiding this comment

DylanDylann Oct 10, 2023 • edited Loading

Choose a reason for hiding this comment

MariaHCD left a comment

Choose a reason for hiding this comment

robertKozik left a comment

Choose a reason for hiding this comment

OSBotify commented Oct 10, 2023

OSBotify commented Oct 11, 2023

OSBotify commented Oct 12, 2023

DylanDylann commented Oct 5, 2023 •

edited

Loading

robertKozik commented Oct 9, 2023 •

edited

Loading

DylanDylann Oct 10, 2023 •

edited

Loading