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

Fix/regression 18110 composer should have the same height in other platforms #19516

Merged
merged 15 commits into from
Jul 24, 2023

Conversation

dukenv0307
Copy link
Contributor

@dukenv0307 dukenv0307 commented May 24, 2023

Details

Composer in Android should have the same height in other platforms

Fixed Issues

$ #18110
PROPOSAL: #18110 (comment)
$ #19358

Tests

  1. Open any chat
  2. Lose focus from compose box
  3. Verify Composer in all platforms should have the same height and hover over compose box and observe that few area above and below 'Write something...'
  4. Verify app should display edit pointer on the whole compose box and on double click, it shouldn't select placeholder text
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  1. Open any chat
  2. Lose focus from compose box
  3. Verify Composer in all platforms should have the same height and hover over compose box and observe that few area above and below 'Write something...'
  4. Verify app should display edit pointer on the whole compose box and on double click, it shouldn't select placeholder text
  • 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 / Chrome
    • iOS / native
    • iOS / 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 approved by marketing by adding the Waiting for Copy label for a copy review 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
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • 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(themeColors.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 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 author checklist, including those that don't apply to this PR.

Screenshots/Videos 18110

Web
Web.mov
Mobile Web - Chrome
chrome.mp4
Mobile Web - Safari
safari.mp4
Desktop
Desktop.mov
iOS
ios.mov
Android
Android.mov

Screenshots/Videos 19358

Web web-1 web-2 web-3
Mobile Web - Chrome mb 1 mb 2 mb 3
Mobile Web - Safari mb 1 mb 2 mb 3
Desktop desktop1 desktop 2 desktop 3
iOS ios 1 ios 2 ios 3
Android Android 1 Android 2 Android 3

@dukenv0307 dukenv0307 changed the title Fix/regression 18110 Fix/regression 18110 composer should have the same height in other platforms May 25, 2023
@dukenv0307 dukenv0307 marked this pull request as ready for review May 25, 2023 03:46
@dukenv0307 dukenv0307 requested a review from a team as a code owner May 25, 2023 03:46
@melvin-bot melvin-bot bot requested review from MariaHCD and removed request for a team May 25, 2023 03:46
@melvin-bot
Copy link

melvin-bot bot commented May 25, 2023

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

@dukenv0307
Copy link
Contributor Author

@MariaHCD I added the link to the issue is "#18110", but right format is "https://github.com/Expensify/App/issues/", so please help to assign reviewer again. Sorry for this inconvenience.

@@ -426,6 +426,10 @@ class Composer extends React.Component {
}

render() {
let paddingValue = 5;
if (this.props.numberOfLines === 1) paddingValue = 9;
Copy link
Collaborator

@mananjadhav mananjadhav May 25, 2023

Choose a reason for hiding this comment

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

Can this be moved to styles? I think it doesn't make sense to have styling added as code in render. Better to get it from styles.

Copy link
Contributor Author

@dukenv0307 dukenv0307 May 25, 2023

Choose a reason for hiding this comment

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

I just moved it to StyleUtils. @mananjadhav please check again

@mananjadhav
Copy link
Collaborator

@dukenv0307 Can you remove the word REGRESSION and just keep the linked issue?

@dukenv0307
Copy link
Contributor Author

@dukenv0307 Can you remove the word REGRESSION and just keep the linked issue?

I updated

@MariaHCD MariaHCD requested review from tgolen and removed request for MariaHCD May 25, 2023 08:10
tgolen
tgolen previously approved these changes May 29, 2023
mananjadhav
mananjadhav previously approved these changes May 29, 2023
Copy link
Collaborator

@mananjadhav mananjadhav left a comment

Choose a reason for hiding this comment

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

thanks for the changes @dukenv0307. I'll finish the checklist today.

@mananjadhav
Copy link
Collaborator

mananjadhav commented May 29, 2023

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 / Chrome
    • iOS / native
    • iOS / 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 approved by marketing by adding the Waiting for Copy label for a copy review 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 */
    • 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(themeColors.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 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

Web web-composer-height
web-cusor-pointer-composer-size.mov
Mobile Web - Chrome mweb-chrome-composer-height
Mobile Web - Safari mweb-safari-composer-height
Desktop desktop-composer-height
desktop-cusor-pointer-composer-size.mov
iOS ios-composer-height
Android android-composer-height-2

@mananjadhav
Copy link
Collaborator

mananjadhav commented May 29, 2023

@dukenv0307 for all my Android emulators, the height shows up as 38.2, unlike 38 in your screenshot (and other platforms).

android-composer-height-2 android-composer-height-1

cc - @tgolen

@dukenv0307
Copy link
Contributor Author

dukenv0307 commented May 30, 2023

I tested this bug on main and the height shows up is 38.2 and this bug is not related to bug 18110. Should we fix this bug in another PR or another issue?

Screenshot 2023-05-30 at 17 36 27

@mananjadhav
Copy link
Collaborator

I think it's best to fix in another PR. Thanks for highlighting that. Can you take the latest pull for main and resolve conflicts?

@dukenv0307 dukenv0307 dismissed stale reviews from mananjadhav and tgolen via 42860a0 May 31, 2023 16:49
@dukenv0307
Copy link
Contributor Author

@mananjadhav I just updated.

@mananjadhav
Copy link
Collaborator

@tgolen did you get a chance to look at the previous comments?

@mananjadhav
Copy link
Collaborator

Quick bump @tgolen

@dukenv0307
Copy link
Contributor Author

dukenv0307 commented Jun 7, 2023

@mananjadhav I just saw that ReportActionItemMessageEdit also used style textInputComposeSpacing, so I think we also need to update this style by getContainerComposeStyle

<View style={styles.textInputComposeSpacing}>

@dukenv0307
Copy link
Contributor Author

@mananjadhav @tgolen Please help review this PR to complete it when you have time.

@mananjadhav
Copy link
Collaborator

Thanks for the bump @dukenv0307. Can you resolve the conflicts please?

@tgolen I've tested this, can you please take a look at the PR?

@dukenv0307
Copy link
Contributor Author

@mananjadhav I resolved the conflict and also updated style for wrap view of composer in ReportActionItemMessageEdit as mentioned in this comment #19516 (comment). Please help to check again.

@dukenv0307
Copy link
Contributor Author

@tgolen Friendly bump to help us to take a look at the PR.

@dukenv0307
Copy link
Contributor Author

@mananjadhav @tgolen Friendly bump.

@dukenv0307
Copy link
Contributor Author

@mananjadhav What we should do to move forward with this PR?

@tgolen
Copy link
Contributor

tgolen commented Jul 24, 2023

Hi! I was out on sabbatical for 2 months. Next time, if I (or anyone from Expensify) doesn't respond in a couple of days, please start asking for help in Slack to see what is going on and move forward with urgency on issues, not just waiting for an update indefinitely.

@tgolen tgolen merged commit 2200b81 into Expensify:main Jul 24, 2023
@OSBotify
Copy link
Contributor

✋ 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

🚀 Deployed to staging by https://github.com/tgolen in version: 1.3.45-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.45-7 🚀

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

paddingTop: paddingValue,
paddingBottom: paddingValue,
};
}
Copy link
Contributor

Choose a reason for hiding this comment

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

✋ Coming from #26222

The composer padding is changed inconsistently due to the number of lines changing between 3 or more, it's noticeable while the composer is full size.

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.

5 participants