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.

Sign up for GitHub

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

Jump to bottom

fix: keyboard not dismissed #53907

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

fix: keyboard not dismissed #53907

wants to merge 6 commits into from
+273 −171

Conversation

daledah
Copy link
Contributor

@daledah daledah commented Dec 11, 2024 •
edited
Loading

Explanation of Change

Fixed Issues

$ #53196
PROPOSAL: #53196 (comment)

Tests

  1. Open a chat that has some messages
  2. Tap on compose box to open keyboard.
  3. Tap anywhere outside keyboard area
  4. Verify that: Keyboard is dismissed
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  1. Open a chat that has some messages
  2. Tap on compose box to open keyboard.
  3. Tap anywhere outside keyboard area
  4. Verify that: Keyboard is dismissed
  • 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 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 used JaimeGPT to get English > Spanish translation. I then posted it 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.ts 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.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • 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
Screen.Recording.2024-12-11.at.16.36.31.mov
Android: mWeb Chrome
Screen.Recording.2024-12-11.at.16.47.19.mov
iOS: Native
Screen.Recording.2024-12-12.at.10.36.02.mov
iOS: mWeb Safari
Screen.Recording.2024-12-11.at.16.51.36.mp4
MacOS: Chrome / Safari
Screen.Recording.2024-12-11.at.15.58.37.mov
MacOS: Desktop
Screen.Recording.2024-12-11.at.16.55.54.mov

@daledah daledah marked this pull request as ready for review December 12, 2024 03:38
@daledah daledah requested a review from a team as a code owner December 12, 2024 03:38
@melvin-bot melvin-bot bot requested review from alitoshmatov and removed request for a team December 12, 2024 03:38
@melvin-bot Melvin Bot
Copy link

melvin-bot bot commented Dec 12, 2024

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

@alitoshmatov
Copy link
Contributor

@daledah Can you resolve conflicts

alitoshmatov
alitoshmatov reviewed Dec 17, 2024
View reviewed changes
src/pages/home/report/PureReportActionItem.tsx Outdated
@@ -296,7 +296,7 @@ function PureReportActionItem({
}: PureReportActionItemProps) {
const {translate} = useLocalize();
const {shouldUseNarrowLayout} = useResponsiveLayout();
const reportID = report?.reportID ?? '';
const reportID = report?.reportID ?? `${CONST.DEFAULT_NUMBER_ID}`;
Copy link
Contributor

Choose a reason for hiding this comment

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

@daledah Why this changes are in this PR? Do main does not have this changes already, I assume when eslint rule is added all the refactoring is also made to app

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's not added in main. I tried to fix all errors, but turns out we need a lot (20-ish) of file changes. Do you think we should continue to make these changes or just ignore it and move on?

Copy link
Contributor

Choose a reason for hiding this comment

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

https://expensify.slack.com/archives/C01GTK53T8Q/p1734427537784129 so this is a new eslint which effects a lot of places. It looks like everyone is handling it in their own PR. @daledah Let's update the code according to eslint rule only in the file we are meant to originally change.

@alitoshmatov
Copy link
Contributor

Wow, this is a lot of changes, I think it is too much for one PR, and is way beyond our scope. I believe this much change might come with a lot of regressions.
@daledah As I said above, we should have only changed files that are related to our original change. Sorry if I misunderstood you, I didn't know you meant the count of files when you said

-we need a lot (20-ish) of file changes

Anyways, I am not sure what our next step should be. @AndrewGable what do you think of whole situation?

alitoshmatov
alitoshmatov reviewed Dec 22, 2024
View reviewed changes
src/components/ReportActionItem/MoneyRequestPreview/MoneyRequestPreviewContent.tsx

const policy = PolicyUtils.getPolicy(iouReport?.policyID);
const isMoneyRequestAction = ReportActionsUtils.isMoneyRequestAction(action);
const transactionID = isMoneyRequestAction ? ReportActionsUtils.getOriginalMessage(action)?.IOUTransactionID : '-1';
const transactionID = isMoneyRequestAction ? ReportActionsUtils.getOriginalMessage(action)?.IOUTransactionID : undefined;
Copy link
Contributor

Choose a reason for hiding this comment

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

Any reason why used undefined instead of CONST.DEFAULT_NUMBER_ID here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

transactionID is string, so we can’t set it to CONST.DEFAULT_NUMBER_ID. Also, undefined and CONST.DEFAULT_NUMBER_ID has the same effect here, as they’re both falsy.

src/components/ReportActionItem/MoneyRequestPreview/MoneyRequestPreviewContent.tsx
@@ -186,7 +186,7 @@ function MoneyRequestPreviewContent({
};

const showContextMenu = (event: GestureResponderEvent) => {
if (!shouldDisplayContextMenu) {
if (!shouldDisplayContextMenu || !reportID) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this change needed, I don't how it is related to eslint problem, and why can't we leave it as it is?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

showContextMenuForReport requires truthy reportID, so we can early return. To prevent this we have to change showContextMenuForReport inputs but it will lead to even more changes.

@AndrewGable
Copy link
Contributor

I'd be curious how this PR will relate to this P/S

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@alitoshmatov alitoshmatov alitoshmatov left review comments

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@daledah @alitoshmatov @AndrewGable