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

Solved closing of keyboard on changing text field on profile page #9441

Merged
merged 76 commits into from
Sep 6, 2022

Conversation

liyamahendra
Copy link
Contributor

@liyamahendra liyamahendra commented Jun 14, 2022

Details

Fixed Issues

$ #9234

Tests

Mobile web:

  1. Click on Settings and select 'Profile'
  2. Click on 'First name' text input field. Notice the keyboard pop-up.
  3. Now click on 'Last name' text input field. Make sure you click the text box where the 'Last name' label is and not inside the empty background.4.
  4. Verify that the keyboard is not dismissed.
  • Verify that no errors appear in the JS console

PR Review Checklist

Contributor (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 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 included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • iOS / native
    • Android / native
    • iOS / Safari
    • Android / Chrome
    • MacOS / Chrome
    • 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 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 was added in all src/languages/* files
    • I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team 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
  • 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 */
    • Any functional components have the displayName property
    • 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 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 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.
  • I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

PR 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 verified tests pass on all platforms & I tested again on:
    • iOS / native
    • Android / native
    • iOS / Safari
    • Android / Chrome
    • MacOS / Chrome
    • 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 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 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 was added in all src/languages/* files
    • I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team 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 */
    • Any functional components have the displayName property
    • 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 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 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

QA Steps

Below steps are specifically for testing on mobile web.

  1. Click on Settings and select 'Profile'
  2. Click on 'First name' text input field. Notice the keyboard pop-up.
  3. Now click on 'Last name' text input field. Make sure you click the text box where the 'Last name' label is and not inside the empty background.4.
  4. The keyboard shown from step 2 should remain visible and not hide/dismiss.
  • Verify that no errors appear in the JS console

Screenshots

Web

Screenshot 2022-06-14 at 12 17 48 PM

Mobile Web

Simulator Screen Shot - iPhone 13 - 2022-06-14 at 12 16 46

Desktop

image

iOS

Simulator Screen Shot - iPhone 13 - 2022-06-14 at 13 01 16

Android

Screenshot_20220614_140733

@liyamahendra liyamahendra requested a review from a team as a code owner June 14, 2022 09:10
@melvin-bot melvin-bot bot requested review from marcochavezf and rushatgabhane and removed request for a team June 14, 2022 09:11
@github-actions
Copy link
Contributor

github-actions bot commented Jun 14, 2022

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@liyamahendra
Copy link
Contributor Author

I have read the CLA Document and I hereby sign the CLA

@rushatgabhane
Copy link
Member

@liyamahendra can you please add a new comment - "recheck" to trigger the CLA bot

@liyamahendra
Copy link
Contributor Author

recheck

Copy link
Member

@rushatgabhane rushatgabhane left a comment

Choose a reason for hiding this comment

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

@liyamahendra

There are a few bug -

  • Fix error message is showing up on editing inputs
  • The checkbox "Set timezone automatically" isn't toggling
  • Clicking save button after making changes doesn't seem to do anything

Any ideas on how we can fix them?

Screen.Recording.2022-06-15.at.7.07.01.PM.mov

@liyamahendra
Copy link
Contributor Author

liyamahendra commented Jun 15, 2022

Any ideas on how we can fix them?

@rushatgabhane I can definitely look into them. Seeing your shared recording, I couldn't infer why would the error message show-up at bottom. Plus, if there is an error in the Input Fields, the error message is shown below it.

Mind sharing the steps how can I reproduce what you saw / happened with you?

@rushatgabhane
Copy link
Member

rushatgabhane commented Jun 15, 2022

Mind sharing the steps how can I reproduce what you saw / happened with you

  1. Click first name TextInput and modify it.
  2. Click anywhere outside the TextInput.

I hope this helps!

@liyamahendra
Copy link
Contributor Author

@rushatgabhane Thank you - the steps did help!

I've made the changes. Attached is the screencast after the changes.

update.mp4

src/pages/settings/Profile/ProfilePage.js Outdated Show resolved Hide resolved
src/pages/settings/Profile/ProfilePage.js Outdated Show resolved Hide resolved
@rushatgabhane
Copy link
Member

left a note here #9234 (comment)

@luacmartins luacmartins self-requested a review June 23, 2022 16:39
@luacmartins
Copy link
Contributor

@rushatgabhane let me know once you are done reviewing this since I wanna check the Form refactor portion of this PR.

src/CONST.js Outdated Show resolved Hide resolved
src/CONST.js Outdated Show resolved Hide resolved
src/pages/settings/Profile/ProfilePage.js Show resolved Hide resolved
src/pages/settings/Profile/ProfilePage.js Outdated Show resolved Hide resolved
src/pages/settings/Profile/ProfilePage.js Outdated Show resolved Hide resolved
src/pages/settings/Profile/ProfilePage.js Outdated Show resolved Hide resolved
@luacmartins
Copy link
Contributor

@liyamahendra this is more dependant on you than us! I feel like the delay has been caused by the code not following our guidelines and several bugs being caught during review. The fastest way to get PRs merged is to read our guidelines and make sure that your code is following it, as well as testing your changes well in all platforms before making them available for review - this reduces the amount of back and forth!

@luacmartins
Copy link
Contributor

@liyamahendra we have conflicts again, can you please address those? @rushatgabhane do you still have any pending comments here?

@rushatgabhane
Copy link
Member

rushatgabhane commented Aug 31, 2022

Reviewing now.

src/pages/settings/Profile/ProfilePage.js Outdated Show resolved Hide resolved
src/pages/settings/Profile/ProfilePage.js Outdated Show resolved Hide resolved
src/pages/settings/Profile/ProfilePage.js Outdated Show resolved Hide resolved
Copy link
Member

@rushatgabhane rushatgabhane left a comment

Choose a reason for hiding this comment

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

Click on the avatar picker and upload an avatar. Verify that no loading indicator appears, and that your avatar updates immediately after you click "Save" (the "Save" button in the cropping modal). Hard refresh () the page, and verify that the new avatar is persisted.

@liyamahendra In PR #10235, the above feature was added ^

But our PR is breaking it.

@rushatgabhane
Copy link
Member

@luacmartins just noting that the submit button doesn't float above keyboard.

But this is an issue related to Form.js We should (if we want to) fix it in another issue by add a prop which would wrap the Button with FixedFooter.

Screen.Recording.2022-09-01.at.1.58.16.AM.mov

@luacmartins
Copy link
Contributor

@liyamahendra I think the checks will pass once @rushatgabhane fills his C+ reviewer checklist. @rushatgabhane will you have some time to review this again today?

Copy link
Member

@rushatgabhane rushatgabhane left a comment

Choose a reason for hiding this comment

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

@liyamahendra thanks for your patience and fixing everything.

Requesting a change to use loadashGet (to prevent app crash)

src/pages/settings/Profile/ProfilePage.js Outdated Show resolved Hide resolved
src/pages/settings/Profile/ProfilePage.js Outdated Show resolved Hide resolved
rushatgabhane
rushatgabhane previously approved these changes Sep 5, 2022
Copy link
Member

@rushatgabhane rushatgabhane left a comment

Choose a reason for hiding this comment

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

@luacmartins LGTM! 🎉

PR Reviewer Checklist
  • 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 verified tests pass on all platforms & I tested again on:
    • iOS / native
    • Android / native
    • iOS / Safari
    • Android / Chrome
    • MacOS / Chrome
    • 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 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 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 was added in all src/languages/* files
    • I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team 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 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 */
    • Any functional components have the displayName property
    • 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 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 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.
  • I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Copy link
Contributor

@luacmartins luacmartins left a comment

Choose a reason for hiding this comment

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

@liyamahendra we are really close! Left comments to remove some empty lines and some constants that were defined twice (probably due to a bad conflict resolution). Let's get this addressed and merged today!

src/CONST.js Outdated Show resolved Hide resolved
src/pages/settings/Profile/ProfilePage.js Outdated Show resolved Hide resolved
src/pages/settings/Profile/ProfilePage.js Outdated Show resolved Hide resolved
src/pages/settings/Profile/ProfilePage.js Show resolved Hide resolved
@luacmartins
Copy link
Contributor

Gonna merge, since @rushatgabhane had already approved this as well! Thanks for your patience @liyamahendra!

@luacmartins luacmartins merged commit 1708742 into Expensify:main Sep 6, 2022
@liyamahendra liyamahendra deleted the 9234 branch September 6, 2022 08:41
@OSBotify
Copy link
Contributor

OSBotify commented Sep 6, 2022

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@liyamahendra
Copy link
Contributor Author

@luacmartins With regards to the bounty you mentioned, how will that happen? Do I've to do anything? Please advise.

@luacmartins
Copy link
Contributor

luacmartins commented Sep 7, 2022

@liyamahendra the process is described here. I'm a bit confused by this comment though, did you already get this payment?

@liyamahendra
Copy link
Contributor Author

Yes, I received the original payment of $250. Upwork auto approves the milestone payment after 14 days of submission of work. Thank you for sharing the link to the process.

@OSBotify
Copy link
Contributor

OSBotify commented Sep 8, 2022

🚀 Deployed to staging by @luacmartins in version: 1.1.98-0 🚀

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

<ScrollView style={styles.flex1} contentContainerStyle={styles.p5}>
<Form
style={[styles.flexGrow1, styles.ph5]}
formID={CONST.PROFILE_SETTINGS_FORM}
Copy link
Contributor

Choose a reason for hiding this comment

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

FYI now'days we put the form IDs here:

App/src/ONYXKEYS.js

Lines 171 to 176 in ff5affd

FORMS: {
ADD_DEBIT_CARD_FORM: 'addDebitCardForm',
REQUEST_CALL_FORM: 'requestCallForm',
REIMBURSEMENT_ACCOUNT_FORM: 'reimbursementAccount',
WORKSPACE_SETTINGS_FORM: 'workspaceSettingsForm',
},

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.

6 participants