Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add mention suggestions #18469

Merged
merged 16 commits into from
May 10, 2023
Merged

Conversation

szebniok
Copy link
Contributor

@szebniok szebniok commented May 5, 2023

Details

Fixed Issues

$ #17890

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

Users you've chatted with before

  1. Enter @ sign into the text input
  2. Some suggestions should pop up
  3. Type in a few characters
  4. Observe that the suggestions got narrower (if they exist, and they match the typed characters)
  5. Tap on one of the suggestions
  6. Verify that the suggestion is inserted into the text input

Users you haven't chatted with before

  1. Enter @ sign into the text input
  2. Type in the whole email of a user that you haven't chatted with before (e.g. random@gmail.com)
  3. Tap on the suggestion that appears
  4. Verify that the suggestion is inserted into the text input
  • 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
    • 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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
Screen.Recording.2023-05-08.at.14.21.21.mov
Mobile Web - Chrome
Screen.Recording.2023-05-09.at.11.58.48.mov
Mobile Web - Safari
Screen.Recording.2023-05-09.at.12.29.37.mov
Desktop
Screen.Recording.2023-05-08.at.14.26.26.mov
iOS
Screen.Recording.2023-05-09.at.12.27.32.mov
Android
Screen.Recording.2023-05-09.at.12.25.54.mov

@szebniok szebniok marked this pull request as ready for review May 9, 2023 10:30
@szebniok szebniok requested a review from a team as a code owner May 9, 2023 10:30
@melvin-bot melvin-bot bot requested review from 0xmiros and puneetlath and removed request for a team May 9, 2023 10:30
@melvin-bot
Copy link

melvin-bot bot commented May 9, 2023

@puneetlath @0xmiroslav 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]

ios/Podfile.lock Outdated Show resolved Hide resolved
@0xmiros
Copy link
Contributor

0xmiros commented May 9, 2023

If we show suggestions in full width and above composer, what's Make auto-complete component work inline for?
cc: @puneetlath

position

@0xmiros
Copy link
Contributor

0xmiros commented May 9, 2023

BUG1:

  • write some text message
  • add mention @ and type 2 letters to show suggestions
  • press Esc key to cancel mention suggestion
  • now full composer text is cleared
bug1.mov

Question:
Is it designed to show suggestions only after 2 letters?
On other platforms like slack and discord, suggestions show immediately after adding @

src/components/MentionSuggestions.js Outdated Show resolved Hide resolved
src/components/MentionSuggestions.js Outdated Show resolved Hide resolved
@szebniok
Copy link
Contributor Author

szebniok commented May 9, 2023

BUG1:

  • write some text message
  • add mention @ and type 2 letters to show suggestions
  • press Esc key to cancel mention suggestion
  • now full composer text is cleared

bug1.mov
Question: Is it designed to show suggestions only after 2 letters? On other platforms like slack and discord, suggestions show immediately after adding @

@0xmiroslav
Regarding BUG1: The behaviour is the same for the existing emoji suggestions, and I wasn't sure If it's a bug. I could fix it with the following code change inside ReportActionCompose.js (I'll commit it right now):
image

Regarding the question: I think the emoji suggestions also appear after 2 letters, and I did the same thing here. I can easily change it (I'll commit it as well).

@0xmiros
Copy link
Contributor

0xmiros commented May 9, 2023

Mention logic should be a bit different from emoji logic.
If you check other platforms, emoji suggestions show after :xy but mention suggestions show after @

@szebniok
Copy link
Contributor Author

szebniok commented May 9, 2023

I've noticed small bug after I've implemented the feedback, working on it now

@szebniok
Copy link
Contributor Author

szebniok commented May 9, 2023

I've noticed small bug after I've implemented the feedback, working on it now

fixed

@puneetlath
Copy link
Contributor

If we show suggestions in full width and above composer, what's #16078 for?

That's a refactor of the auto-suggestion component, but it's not a blocker for this.

BUG1:

I've seen a bug report for this for emojis as well, so I don't think we need to fix it here. (unless @szebniok already has).

@perunt
Copy link
Contributor

perunt commented May 9, 2023

BUG1:

It seems like this is the default behavior of the composer, as it is reproducible with plain text as well

@szebniok
Copy link
Contributor Author

szebniok commented May 9, 2023

The fix that I've commited closes the emoji/mention suggestions on the first ESC press (if they're present), and clears the text input on the second press.

@0xmiros
Copy link
Contributor

0xmiros commented May 9, 2023

The fix that I've commited closes the emoji/mention suggestions on the first ESC press (if they're present), and clears the text input on the second press.

This can be out of scope but you already did good job! I like this behavior. Thoughts @puneetlath?

I believe this is not a blocker but just to confirm:
@here can be added in suggestions list in group chat?

@puneetlath
Copy link
Contributor

This can be out of scope but you already did good job! I like this behavior. Thoughts @puneetlath?

Agreed, that seems good to me too!

@here can be added in suggestions list in group chat?

Ah, yes. @here should be an option. We can add that in follow-up though.

@0xmiros
Copy link
Contributor

0xmiros commented May 9, 2023

Small bug:

  • Type test @
  • Move cursor at the beginning before test
  • Suggestions don't disappear
bug2.mov

This doesn't happen on emoji code

@0xmiros
Copy link
Contributor

0xmiros commented May 9, 2023

Bug but NAB since it also happens on emoji suggestions (@puneetlath we can create new issue for tracking if not already reported)

Arrow up/down always loop with 5 even though suggestions list is less than 5

bug3.mov

@0xmiros
Copy link
Contributor

0xmiros commented May 9, 2023

How do we handle phone users? They're not recognized as mention because phone number has spaces

bug4.mov

@0xmiros
Copy link
Contributor

0xmiros commented May 10, 2023

I think QA Steps is wrong. Is there any difference between Recent report and New report in design doc?
Whatever report is, I always get suggestions list after @

@puneetlath
Copy link
Contributor

In theory, there will always be at least one suggestion of Concierge.

@puneetlath
Copy link
Contributor

I updated the QA steps. Do you think that's better @0xmiroslav?

@0xmiros
Copy link
Contributor

0xmiros commented May 10, 2023

I updated the QA steps. Do you think that's better @0xmiroslav?

yes that's clear. So list data is not related to report but contacts

@0xmiros
Copy link
Contributor

0xmiros commented May 10, 2023

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 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 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
web1.mov
web2.mov
Mobile Web - Chrome
mchrome.mov
Mobile Web - Safari
msafari.mov
Desktop
desktop.mov
iOS
ios.mov
Android
android.mov

@puneetlath
Copy link
Contributor

Alright! Going to go ahead and merge this baby.

Copy link
Contributor

@0xmiros 0xmiros left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here's summary of follow-up issues:

  1. suggestions view position (Add mention suggestions #18469 (comment))
  2. suggestions don't disappear when move cursor to the start position (Add mention suggestions #18469 (comment))
  3. Arrow up/down always loop with 5 even though suggestions list is less than 5 (Add mention suggestions #18469 (comment))
  4. support phone users
  5. suggestions still remaining after send and composer cleared
  6. space is added endlessly while keep selecting suggested user (Add mention suggestions #18469 (review))
  7. arrow index is not within range and show console error (Add mention suggestions #18469 (comment))
  8. add myself in suggestions list
  9. add @here in suggestions list, maybe only for group chat

@puneetlath
Copy link
Contributor

Thanks for making the list!

  1. suggestions view position (Add mention suggestions #18469 (comment))

Will be fixed automatically in: #16078

  1. suggestions don't disappear when move cursor to the start position (Add mention suggestions #18469 (comment))

Looks like it was already fixed by @szebniok in this PR

  1. Arrow up/down always loop with 5 even though suggestions list is less than 5 (Add mention suggestions #18469 (comment))

Will be fixed in: #16426

  1. support phone users

Created issue: #18729

  1. suggestions still remaining after send and composer cleared

Reported here: https://expensify.slack.com/archives/C049HHMV9SM/p1683751749650109

  1. space is added endlessly while keep selecting suggested user (Add mention suggestions #18469 (review))

Issue here: #18742

  1. arrow index is not within range and show console error (Add mention suggestions #18469 (comment))

Created issue here: #18744

  1. add myself in suggestions list
  2. add @here in suggestions list, maybe only for group chat

Created issue for this here: #18746

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/puneetlath in version: 1.3.13-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/Beamanator in version: 1.3.13-5 🚀

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

}

LayoutAnimation.configureNext(LayoutAnimation.create(50, LayoutAnimation.Types.easeInEaseOut, LayoutAnimation.Properties.opacity));

this.setState(nextState);
}

calculateMentionSuggestion() {
if (this.state.selection.end < 1) {
Copy link
Contributor

@dukenv0307 dukenv0307 May 15, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@szebniok This change caused this bug. Could you help to explain why we need to add this? Could we use !this.state.value instead of this.state.selection.end < 1?

cc @0xmiroslav @puneetlath

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dukenv0307 this is how it's done for the existing emoji suggestion feature, so I'm guessing we just replicated that behavior for mentions.

Copy link
Collaborator

@Santhosh-Sellavel Santhosh-Sellavel Jun 3, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should have called the resetSuggestions as we do for Emoji Suggestions but we missed that here.

@mananjadhav
Copy link
Collaborator

We added the highlightedMentionIndex in this PR but we didn't reset the index to 0 after selection, which caused this bug #18844.

@mananjadhav
Copy link
Collaborator

The MENTION_REPLACER caused the this issue. I think this was an odd cause and regex are difficult to test. But testing emojis next to auto completing could have picked this one.

I don't think any checklist update is required.

@Santhosh-Sellavel
Copy link
Collaborator

This PR caused a regression here. Refer to PR for more.

const mentionCode = `@${mentionObject.alternateText}`;
const commentAfterAtSignWithMentionRemoved = this.state.value.slice(this.state.atSignIndex).replace(CONST.REGEX.MENTION_REPLACER, '');

this.updateComment(`${commentBeforeAtSign}${mentionCode} ${commentAfterAtSignWithMentionRemoved}`, true);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Regardless of whether the commentAfterAtSignWithMentionRemoved begins with a space or not, we consistently include an additional space. This caused a regression.

Comment on lines +1209 to +1211
personalDetails: {
key: ONYXKEYS.PERSONAL_DETAILS,
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we didn't need this b/c we already had the hoc withPersonalDetails(),

if ((e.key === CONST.KEYBOARD_SHORTCUTS.ENTER.shortcutKey || e.key === CONST.KEYBOARD_SHORTCUTS.TAB.shortcutKey) && this.state.suggestedEmojis.length) {
const suggestionsExist = this.state.suggestedEmojis.length > 0 || this.state.suggestedMentions.length > 0;

if ((e.key === CONST.KEYBOARD_SHORTCUTS.ENTER.shortcutKey || e.key === CONST.KEYBOARD_SHORTCUTS.TAB.shortcutKey) && suggestionsExist) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Coming from #19624

Not a regression. We want to skip the selection when pressing Shift + Enter as Slack does.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.