fix: Unable to proceed to the next tab from Invite new members with Enter key. #44542

Krishna2323 · 2024-06-27T12:46:12Z

Details

Fixed Issues

$ #43821
PROPOSAL: #43821 (comment)

Tests

Open workspace members page > Invite member
Select users using keyboard > Press enter when no option is selected
Verify you are proceeded to the next tab
Open a group chat > Click on header > Select members > Invite
Select users using keyboard > Press enter when no option is selected
Verify you are proceeded to the next tab
Open a room chat > Click on header > Select members > Invite Members
Select users using keyboard > Press enter when no option is selected
Verify selected members are invited

Verify that no errors appear in the JS console

Offline tests

Open workspace members page > Invite member
Select users using keyboard > Press enter when no option is selected
Verify you are proceeded to the next tab
Open a group chat > Click on header > Select members > Invite
Select users using keyboard > Press enter when no option is selected
Verify you are proceeded to the next tab
Open a room chat > Click on header > Select members > Invite Members
Select users using keyboard > Press enter when no option is selected
Verify selected members are invited

QA Steps

Open workspace members page > Invite member
Select users using keyboard > Press enter when no option is selected
Verify you are proceeded to the next tab
Open a group chat > Click on header > Select members > Invite
Select users using keyboard > Press enter when no option is selected
Verify you are proceeded to the next tab
Open a room chat > Click on header > Select members > Invite Members
Select users using keyboard > Press enter when no option is selected
Verify selected members are invited

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

android_native.mp4

Android: mWeb Chrome

android_chrome.mp4

iOS: Native

ios_native.mp4

iOS: mWeb Safari

ios_safari.mp4

MacOS: Chrome / Safari

web_chrome.mp4

MacOS: Desktop

desktop_app.mp4

…nter key. Signed-off-by: Krishna Gupta <[email protected]>

melvin-bot · 2024-06-27T12:46:17Z

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

Ollyws · 2024-06-28T08:42:54Z

src/pages/InviteReportParticipantsPage.tsx

@@ -197,7 +197,7 @@ function InviteReportParticipantsPage({betas, personalDetails, report, didScreen
                onSubmit={inviteUsers}
                containerStyles={[styles.flexReset, styles.flexGrow0, styles.flexShrink0, styles.flexBasisAuto]}
                enabledWhenOffline
-                disablePressOnEnter
+                disablePressOnEnter={false}


Why are we passing {false} as opposed to just removing the prop?

Silly mistake, sorry. I was looking at FormWrapper component which has true as the default value of disablePressOnEnter. Updated now.

Signed-off-by: Krishna Gupta <[email protected]>

Ollyws · 2024-07-03T12:11:19Z

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 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 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 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.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

01_Android_Native.mp4

Android: mWeb Chrome

02_Android_Chrome.mp4

iOS: Native

03_iOS_Native.mp4

iOS: mWeb Safari

04_iOS_Safari.mp4

MacOS: Chrome / Safari

05_MacOS_Chrome.mp4

MacOS: Desktop

06_MacOS_Desktop.mp4

Ollyws

LGTM.

OSBotify · 2024-07-03T16:46:53Z

✋ 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 · 2024-07-03T20:02:39Z

🚀 Deployed to staging by https://github.com/blimpich in version: 9.0.4-0 🚀

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

OSBotify · 2024-07-04T22:15:06Z

🚀 Cherry-picked to staging by https://github.com/tgolen in version: 9.0.4-5 🚀

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

OSBotify · 2024-07-10T11:03:29Z

🚀 Deployed to production by https://github.com/Julesssss in version: 9.0.5-13 🚀

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

OSBotify · 2024-07-15T20:22:08Z

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.6-8 🚀

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

fix: Unable to proceed to the next tab from Invite new members with E…

4ac6f30

…nter key. Signed-off-by: Krishna Gupta <[email protected]>

Krishna2323 requested a review from a team as a code owner June 27, 2024 12:46

melvin-bot bot removed the request for review from a team June 27, 2024 12:46

melvin-bot bot requested a review from Ollyws June 27, 2024 12:46

Ollyws reviewed Jun 28, 2024

View reviewed changes

remove disablePressOnEnter prop.

c453158

Signed-off-by: Krishna Gupta <[email protected]>

Ollyws approved these changes Jul 3, 2024

View reviewed changes

melvin-bot bot requested a review from blimpich July 3, 2024 12:12

blimpich approved these changes Jul 3, 2024

View reviewed changes

blimpich merged commit 34d27b6 into Expensify:main Jul 3, 2024
15 of 16 checks passed

github-actions bot mentioned this pull request Jul 3, 2024

Deploy Checklist: New Expensify 2024-07-03 #44782

Closed

melvin-bot bot mentioned this pull request Jul 10, 2024

[HOLD for payment 2024-07-17] [$250] Workspace - Unable to proceed to the next tab from "Invite new members" with Enter key #43821

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix: Unable to proceed to the next tab from Invite new members with Enter key. #44542

fix: Unable to proceed to the next tab from Invite new members with Enter key. #44542

Krishna2323 commented Jun 27, 2024

melvin-bot bot commented Jun 27, 2024

Ollyws Jun 28, 2024 •

edited

Loading

Krishna2323 Jul 2, 2024

Ollyws commented Jul 3, 2024

Ollyws left a comment

OSBotify commented Jul 3, 2024

OSBotify commented Jul 3, 2024

OSBotify commented Jul 4, 2024

OSBotify commented Jul 10, 2024

OSBotify commented Jul 15, 2024

fix: Unable to proceed to the next tab from Invite new members with Enter key. #44542

fix: Unable to proceed to the next tab from Invite new members with Enter key. #44542

Conversation

Krishna2323 commented Jun 27, 2024

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Jun 27, 2024

Ollyws Jun 28, 2024 • edited Loading

Choose a reason for hiding this comment

Krishna2323 Jul 2, 2024

Choose a reason for hiding this comment

Ollyws commented Jul 3, 2024

Reviewer Checklist

Screenshots/Videos

Ollyws left a comment

Choose a reason for hiding this comment

OSBotify commented Jul 3, 2024

OSBotify commented Jul 3, 2024

OSBotify commented Jul 4, 2024

OSBotify commented Jul 10, 2024

OSBotify commented Jul 15, 2024

Ollyws Jun 28, 2024 •

edited

Loading