-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Conversation
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
I have read the CLA Document and I hereby sign the CLA |
@liyamahendra can you please add a new comment - "recheck" to trigger the CLA bot |
recheck |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
@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? |
I hope this helps! |
@rushatgabhane Thank you - the steps did help! I've made the changes. Attached is the screencast after the changes. update.mp4 |
left a note here #9234 (comment) |
@rushatgabhane let me know once you are done reviewing this since I wanna check the Form refactor portion of this PR. |
@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! |
@liyamahendra we have conflicts again, can you please address those? @rushatgabhane do you still have any pending comments here? |
Reviewing now. |
There was a problem hiding this 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.
@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 Screen.Recording.2022-09-01.at.1.58.16.AM.mov |
@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? |
There was a problem hiding this 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)
There was a problem hiding this 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 verified the steps for local testing are in the
- 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 notonIconClick
). - 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
- 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.
- 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. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor) - Any internal methods bound to
this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
) - 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 thatAvatar
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.
There was a problem hiding this 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!
Gonna merge, since @rushatgabhane had already approved this as well! Thanks for your patience @liyamahendra! |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
@luacmartins With regards to the bounty you mentioned, how will that happen? Do I've to do anything? Please advise. |
@liyamahendra the process is described here. I'm a bit confused by this comment though, did you already get this payment? |
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. |
🚀 Deployed to staging by @luacmartins in version: 1.1.98-0 🚀
|
<ScrollView style={styles.flex1} contentContainerStyle={styles.p5}> | ||
<Form | ||
style={[styles.flexGrow1, styles.ph5]} | ||
formID={CONST.PROFILE_SETTINGS_FORM} |
There was a problem hiding this comment.
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:
Lines 171 to 176 in ff5affd
FORMS: { | |
ADD_DEBIT_CARD_FORM: 'addDebitCardForm', | |
REQUEST_CALL_FORM: 'requestCallForm', | |
REIMBURSEMENT_ACCOUNT_FORM: 'reimbursementAccount', | |
WORKSPACE_SETTINGS_FORM: 'workspaceSettingsForm', | |
}, |
Details
Fixed Issues
$ #9234
Tests
Mobile web:
PR Review Checklist
Contributor (PR Author) Checklist
### Fixed Issues
section aboveTests
sectionQA steps
sectiontoggleReport
and notonIconClick
)src/languages/*
filesSTYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)/** comment above it */
displayName
propertythis
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor)this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)PR Reviewer Checklist
### Fixed Issues
section aboveTests
sectionQA steps
sectiontoggleReport
and notonIconClick
).src/languages/*
filesSTYLE.md
) were followedAvatar
, I verified the components usingAvatar
have been tested & I retested again)/** comment above it */
displayName
propertythis
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor)this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)QA Steps
Below steps are specifically for testing on mobile web.
Screenshots
Web
Mobile Web
Desktop
iOS
Android