Fix invited members for admin threads

[narefyev91]

Details

After allowing threads for admin rooms - there were some issues to resolve

Fixed Issues

$ #33738
PROPOSAL: #33738 (comment)

Tests

1. Alice creates a workspace Alice's Apples
2. Alice invites Bob to the workspace
3. Bob creates a room #bagel-lovers that Alice is not in
4. Bob invites Cathy (who is not a member of the workspace) to #bagel-lovers
5. This cause Bob to post a system message to the #admins room of Alice's Apples saying: Bob invited Cathy to #bagel-lovers
6. Alice opens a thread on that system message
7. Alice posts "What up Bob, why did you invite Cathy?" in that thread
8. Confirm Bob is invited to that thread and sees Alice's message
9. Mention by @ should be available
10. Click into the room header and go to Members
11. It shows the member list with options to add/remove

• Verify that no errors appear in the JS console

Offline tests

1. Alice creates a workspace Alice's Apples
2. Alice invites Bob to the workspace
3. Bob creates a room #bagel-lovers that Alice is not in
4. Bob invites Cathy (who is not a member of the workspace) to #bagel-lovers
5. This cause Bob to post a system message to the #admins room of Alice's Apples saying: Bob invited Cathy to #bagel-lovers
6. Alice opens a thread on that system message
7. Alice posts "What up Bob, why did you invite Cathy?" in that thread
8. Confirm Bob is invited to that thread and sees Alice's message
9. Mention by @ should be available
10. Click into the room header and go to Members
11. It shows the member list with options to add/remove

QA Steps

1. Alice creates a workspace Alice's Apples
2. Alice invites Bob to the workspace
3. Bob creates a room #bagel-lovers that Alice is not in
4. Bob invites Cathy (who is not a member of the workspace) to #bagel-lovers
5. This cause Bob to post a system message to the #admins room of Alice's Apples saying: Bob invited Cathy to #bagel-lovers
6. Alice opens a thread on that system message
7. Alice posts "What up Bob, why did you invite Cathy?" in that thread
8. Confirm Bob is invited to that thread and sees Alice's message
9. Mention by @ should be available
10. Click into the room header and go to Members
11. It shows the member list with options to add/remove

• 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
  • 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 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 form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label 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.
• 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

8mb.video-HFf-jgKBs2vF.mp4

Android: mWeb Chrome

8mb.video-Ef6-HVujRQyb.mp4

iOS: Native

8mb.video-mSR-rt3IUl3Y.mp4

iOS: mWeb Safari

8mb.video-3Dv-nc3F8yeb.mp4

MacOS: Chrome / Safari

8mb.video-4wq-qr90Z52d.mp4

MacOS: Desktop

8mb.video-Ha5-ox1Wz5un.mp4

[narefyev91]

Have some issues with building android - but will not block the review

[melvin-bot]

@aimane-chnaif 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]

[narefyev91]

@aimane-chnaif friendly bump on this one

[aimane-chnaif]

reviewing today

[aimane-chnaif]

Please resolve conflict

[aimane-chnaif]

there were some issues to resolve

Can you please add context what issues are fixed?

[aimane-chnaif]

Testing against main, I haven't found any case of thread disabled for system messages.
So I assume this PR only fixes some issues in admin threads.

[aimane-chnaif]

9. Mention @cathy@croissants.com
10. Cathy should be added to the thread

Is this supposed to work? I don't see Cathy is being invited to the thread

My test accounts:

• aiman.chnaif+2@gmail.com: Alice
• aiman.chnaif+31@gmail.com: Bob
• aiman.chnaif+32@gmail.com: Cathy

[narefyev91]

Testing against main, I haven't found any case of thread disabled for system messages. So I assume this PR only fixes some issues in admin threads.

Yup the PR is mostly fixing issues with admin threads - like correct naming in the headers and left section

[narefyev91]

9. Mention @cathy@croissants.com
10. Cathy should be added to the thread

Is this supposed to work? I don't see Cathy is being invited to the thread

My test accounts:

• aiman.chnaif+2@gmail.com: Alice
• aiman.chnaif+31@gmail.com: Bob
• aiman.chnaif+32@gmail.com: Cathy

I think that it is correct behaviour - because here you just mentioned person in thread. Previously just @ was not working

[aimane-chnaif]

If that's the correct behavior, 10. Cathy should be added to the thread should be removed from Tests

[narefyev91]

If that's the correct behavior, 10. Cathy should be added to the thread should be removed from Tests

Updated description and add small fix for broken single thread for same user

[quinthar]

What's the next step and who is doing it, when?

[narefyev91]

What's the next step and who is doing it, when?

I think that @aimane-chnaif will make final test - already saw based on his latest screenshot that flow is working fine. In any case will be here during all day and the weekend to help pushing it asap

[aimane-chnaif]

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(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 form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label 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.
• 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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

[aimane-chnaif]

Before:

After:

[melvin-bot]

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

[blimpich]

Looks good! ✅

[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 production by https://github.com/thienlnam in version: 1.4.31-7 🚀

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