[WorkspaceInviteMemberPage] update welcome note on workspace name change

[Prince-Mendiratta]

Details

With this PR, when the Workspace Invite Member Page is open on one device
and the workspace name is changed from another device, then the welcome
note updates with the new workspace name, if it has not been modified by
the user.

Fixed Issues

$ #16600
PROPOSAL: #16600 (comment)

Tests

• Test 1

1. Login to ND on device 1.
2. Go to Settings > Workspaces > Any workspace > Members > Invite Member.
3. Keep the page open.
4. Login to ND on device 2.
5. Go to Settings > Workspaces > The same workspace > General.
6. Change the Workspace name. Click on save
7. Ensure that the workspace name updates in the welcome note on device
   1.

• Test 2

1. Login to ND on device 1.
2. Go to Settings > Workspaces > Any workspace > Members > Invite Member.
3. Modify the welcome note.
4. Keep the page open.
5. Login to ND on device 2.
6. Go to Settings > Workspaces > The same workspace > General.
7. Change the Workspace name. Click on save
8. Ensure that the workspace name does NOT update in the welcome note on
   device 1.

• Verify that no errors appear in the JS console

Offline tests

Although the PR does not modify any functionality depending on network
changes, the expected offline behaviour is:
If either of the 2 devices are offline, then the changes made to the
workspace name would not be reflected.

QA Steps

Same as 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 / 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 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 correct
    English and 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
  • 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 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 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.mp4

Mobile Web - Chrome

android-mWeb.mp4

Mobile Web - Safari

ios-mWeb.mp4

Desktop

desktop.mp4

iOS

ios.mp4

Android

android.mp4

[MelvinBot]

@youssef-lr @thesahindia One of you needs to 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]

[thesahindia]

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 / Chrome
  • iOS / native
  • iOS / 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 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 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

Screen.Recording.2023-04-19.at.3.07.39.AM.mov

Mobile Web - Chrome

Screen.Recording.2023-04-19.at.3.53.04.AM.mov

Mobile Web - Safari

Screen.Recording.2023-04-19.at.3.39.54.AM.mov

Desktop

Screen.Recording.2023-04-19.at.3.57.14.AM.mov

iOS

Screen.Recording.2023-04-19.at.3.34.50.AM.mov

Android

Screen.Recording.2023-04-19.at.3.47.01.AM.mov

[thesahindia]

Works well!

All yours @youssef-lr

[OSBotify]

✋ 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]

🚀 Deployed to staging by https://github.com/youssef-lr in version: 1.3.3-0 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.3-2 🚀

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