Fix/32280 here mention suggestion fix

[koko57]

Details

Fixed Issues

$ #32280
PROPOSAL: #32280 (comment)

Tests

Prerequisites: you need to have a contact whose name includes "here"

1. Go to any chat
2. Start typing "@here"
3. Choose the "@here" suggestion from the suggestion list
4. Verify that after choosing the suggestion the suggestion list is closed and doesn't reopen
5. Delete a few letters - if there's still @ sing in the composer the suggestion list should appear again.
6. Do the steps 2 - 4 once again.
7. Refresh the page or leave the chat and go back.
8. Verify that after refreshing / or coming back to the chat and focusing the composer "@here" value is visible and the suggestion list doesn't appear.

• Verify that no errors appear in the JS console

Offline tests

QA Steps

Prerequisites: you need to have a contact whose name includes "here"

1. Go to any chat
2. Start typing "@here"
3. Choose the "@here" suggestion from the suggestion list
4. Verify that after choosing the suggestion the suggestion list is closed and doesn't reopen
5. Delete a few letters - if there's still @ sing in the composer the suggestion list should appear again.
6. Do the steps 2 - 4 once again.
7. Refresh the page or leave the chat and go back.
8. Verify that after refreshing / or coming back to the chat and focusing the composer "@here" value is visible and the suggestion list doesn't appear.

• 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
    • 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 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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Screen.Recording.2024-02-27.at.08.05.03.mov

Android: mWeb Chrome

Screen.Recording.2024-02-27.at.07.47.11.mov

iOS: Native

Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-02-27.at.07.46.40.mp4

iOS: mWeb Safari

fix.mp4

MacOS: Chrome / Safari

Screen.Recording.2024-02-27.at.07.30.54.mov

MacOS: Desktop

Screen.Recording.2024-02-27.at.07.35.39.mov

[melvin-bot]

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

[sobitneupane]

@koko57 I can still reproduce the issue. I had to try entering the keyword in two different reports few times to reproduce the issue.

Screen.Recording.2024-03-06.at.18.26.58.mov

cc: @arosiclair

[koko57]

@sobitneupane ok, thanks! I will look into that

[koko57]

@sobitneupane It's strange, I thought that maybe there is a problem with current handles (not including '@domain.com' anymore) bur it looks like the lastSelectedMentionSuggestion gets overwritten with an empty string. I'm not triggering it myself like in the useEffect, so I wonder how it gets cleared. I'll continue investigating it

[koko57]

@sobitneupane looks like this PR #38361 solved the problem, at least I cannot reproduce it now but I think it should be retested

[sobitneupane]

@koko57 Yeah. It is no longer reproducible in my end as well.