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

Feature: Tooltip for workspace chat #45390

Merged
merged 47 commits into from
Aug 7, 2024

Conversation

tienifr
Copy link
Contributor

@tienifr tienifr commented Jul 15, 2024

Details

Display a tooltip the first time user views the workspace chat.

Fixed Issues

$ #45046
PROPOSAL: #45046 (comment)

Tests

  1. Log in as User A, an account that owns a workspace
  2. Invite B, a user that does not yet have an Expensify account
  3. Check B's email for the invitation
  4. Open the new.expensify.com link from the email in a different browser
  5. On A, open the workspace chat
  6. Verify a tooltip shows over the composer's Create button saying Get started! Submit your first expense or ¡Empecemos! Presenta tu primer gasto
  7. Press Create button
  8. Verify the tooltip disappears (or it will automatically disappear in 5 seconds)
  • Verify that no errors appear in the JS console

Offline tests

NA

QA Steps

See Tests

  • 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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • 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 UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design 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

Screenshot_1721983761

Android: mWeb Chrome

Screenshot_1722421486

iOS: Native

Simulator Screenshot - iPhone 15 Pro Max - 2024-07-15 at 16 34 13

iOS: mWeb Safari

Simulator Screenshot - iPhone 15 Pro Max - 2024-07-31 at 17 24 52

MacOS: Chrome / Safari Screenshot 2024-07-30 at 04 59 50
MacOS: Desktop Screenshot 2024-07-15 at 16 36 11

@tienifr
Copy link
Contributor Author

tienifr commented Jul 19, 2024

Update: I had several issues:

  1. When I switch the report, the tooltip is not hidden and moves to some random places in the page
  2. The tooltip position in Safari is not correct, it's always center aligned wrt the target even though the computed position values are correct

@trjExpensify
Copy link
Contributor

@tienifr did you fix those issues or ask for help if you need it? We want to keep this PR moving. CC: @dukenv0307 as you'll have some context on this.

@dukenv0307
Copy link
Contributor

@tienifr Can you update the PR and let me know what's your blocker right now? Thanks

@trjExpensify
Copy link
Contributor

@tienifr you have conflicts. Can you fix those and confirm this is ready for a review today?

@tienifr tienifr marked this pull request as ready for review July 29, 2024 21:47
@tienifr tienifr requested review from a team as code owners July 29, 2024 21:47
@melvin-bot melvin-bot bot removed the request for review from a team July 29, 2024 21:47
Copy link

melvin-bot bot commented Jul 29, 2024

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

@melvin-bot melvin-bot bot requested a review from dukenv0307 July 29, 2024 21:47
@dukenv0307
Copy link
Contributor

@tienifr Is it ready for review?

@trjExpensify
Copy link
Contributor

Bump, @tienifr please confirm this is ready for re-review?

@dubielzyk-expensify
Copy link
Contributor

Other than the bug, the videos above looked good to me!

<View style={pointerStyle} />
</View>
</Animated.View>
<Portal hostName={!shouldUseOverlay ? 'modal' : undefined}>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Teleport the portal to the modal layer, otherwise, the tooltip in any modal/popover would be obscured by that modal. For example the tooltip for QAB.

return;
}
setShouldUseOverlay(false);
hideTooltip();
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Interacting with shouldRender prop causes the target component to re-render thus leads to flickering. I move the logic to hide tooltip from the target component (i.e. composer) to inside the tooltip itself to avoid such flickering.

@tienifr
Copy link
Contributor Author

tienifr commented Aug 7, 2024

@dukenv0307 I fixed the Android bug above and also discovered several other bugs. Added explanations for them above ^. Ready for review.

@dukenv0307
Copy link
Contributor

@tienifr I think we should use the same logic here

@tienifr
Copy link
Contributor Author

tienifr commented Aug 7, 2024

@dukenv0307 Thanks for the suggestions. Updated.

@melvin-bot melvin-bot bot requested a review from deetergp August 7, 2024 17:14
@dukenv0307
Copy link
Contributor

LGTM

Copy link
Contributor

@deetergp deetergp left a comment

Choose a reason for hiding this comment

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

Looks good, thanks!

@deetergp deetergp merged commit 6a6c242 into Expensify:main Aug 7, 2024
16 checks passed
@OSBotify
Copy link
Contributor

OSBotify commented Aug 7, 2024

✋ 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
Copy link
Contributor

OSBotify commented Aug 7, 2024

🚀 Deployed to staging by https://github.com/deetergp in version: 9.0.18-0 🚀

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

@IuliiaHerets
Copy link

This PR is failing for Desktop app because of issue #47169

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.0.18-10 🚀

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

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.

8 participants