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

[CP Staging] Bump react-native-live-markdown to 0.1.82 #43255

Conversation

BartoszGrajdek
Copy link
Contributor

@BartoszGrajdek BartoszGrajdek commented Jun 7, 2024

Details

This PR bumps the version of live markdown

Fixed Issues

$ #41696
$ #39255
$ #42160
$ #17767
$ #14445
$ #15640
$ #41137
$ #41567
$ #42523
$ #41078

Tests

The best course of action would be to go through each of the issues added above and verify if just the changes in react-native-live-markdown were needed to fix them. If so you can test if they are not happening anymore. Here's a list of some of the issues & testing steps:

  1. [HOLD for payment 2024-06-28] [HOLD for payment 2024-06-20][$250] Room-User is allowed to invite via mentions invalid number. #41078
    Check if only valid phone number mentions are allowed
  2. [HOLD for payment 2024-06-20] [HOLD for payment 2024-06-18] [$250] mweb-chat-Unable to type in compose box #42523
    Check if you are able to type in the composer on android mWeb
  3. [HOLD for payment 2024-06-20] [HOLD for payment 2024-06-18] [$500] IOS - Task - Unable to scroll down task description #41567
    Check if you are able to scroll task description input
  4. [HOLD for payment 2024-06-28] [HOLD for payment 2024-06-20] [HOLD for payment 2024-06-18] [$500] mWeb - Chat-Pasting text in compose box makes page moves up and down #41137
    Check if pasting on android mWeb
  5. [HOLD for payment 2024-06-20] [HOLD for payment 2024-06-18] [HOLD for payment 2024-06-06] [HOLD #37374][$1000] Text in some languages gets cut off at the bottom in composer on ios #17767
    Paste text from issue desc and check if it's displayed properly
  6. [PAID] [HOLD for payment 2024-06-18] [$500] Unable to undo copy and pasted text #39255
    Check if you are able to undo copy pasted text
  7. [HOLD for payment 2024-06-20] [HOLD for payment 2024-06-18] Live Markdown treats > space and >nospace equally #41696
    Check if markdown is treating >test and > test differently (the second one should be a quote, the first one just plain text)

Offline tests

QA Steps

  • 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 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 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.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 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.

Screenshots/Videos

Android: Native
android.mov
Android: mWeb Chrome
mweb.chrome.mov
iOS: Native
ios.mov
iOS: mWeb Safari
mweb.safari.mov
MacOS: Chrome / Safari
web.mov
MacOS: Desktop
desktop.mov

@BartoszGrajdek BartoszGrajdek marked this pull request as ready for review June 7, 2024 11:32
@BartoszGrajdek BartoszGrajdek requested a review from a team as a code owner June 7, 2024 11:32
@melvin-bot melvin-bot bot requested review from mollfpr and removed request for a team June 7, 2024 11:32
Copy link

melvin-bot bot commented Jun 7, 2024

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

@BartoszGrajdek
Copy link
Contributor Author

cc @luacmartins

@BartoszGrajdek
Copy link
Contributor Author

cc @tomekzaw @SzymczakJ

@luacmartins luacmartins changed the title Bump react-native-live-markdown to 0.1.82 [CP Staging] Bump react-native-live-markdown to 0.1.82 Jun 7, 2024
@luacmartins luacmartins removed the request for review from mollfpr June 7, 2024 13:46
@ishpaul777
Copy link
Contributor

ishpaul777 commented Jun 7, 2024

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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop

@ishpaul777
Copy link
Contributor

  1. [HOLD] Stop highlighting report mentions in non policy rooms in the Composer #41597

    Check if report mentions in non policy rooms are not highlighted- Not fixed
Screen.Recording.2024-06-07.at.7.29.00.PM.mov

@tomekzaw
Copy link
Contributor

tomekzaw commented Jun 7, 2024

#43255 (comment)

Actually, this wasn't supposed to be fixed, I think it's in the PR description by mistake. Thanks for pointing this out.

@ishpaul777
Copy link
Contributor

ishpaul777 commented Jun 7, 2024

  1. [HOLD for payment 2024-06-28] [HOLD for payment 2024-06-20][$250] Room-User is allowed to invite via mentions invalid number. #41078 Check if only valid phone number mentions are allowed - fixed

Macos Chrome -

Screen.Recording.2024-06-07.at.7.40.30.PM.mov

IOS native -

Screen.Recording.2024-06-07.at.8.29.28.PM.mov

IOS safari -

Screen.Recording.2024-06-07.at.9.00.48.PM.mov

mweb android -

Screen.Recording.2024-06-07.at.9.00.48.PM.mov

Desktop -

Screen.Recording.2024-06-07.at.9.34.43.PM.mov

@ishpaul777
Copy link
Contributor

ishpaul777 commented Jun 7, 2024

  1. [HOLD for payment 2024-06-20] [HOLD for payment 2024-06-18] [$250] mweb-chat-Unable to type in compose box #42523 - Check if you are able to type in the composer on android mWeb - fixed

Mweb - android chrome

WhatsApp.Video.2024-06-07.at.7.44.32.PM.mp4

iOS Native

Screen.Recording.2024-06-07.at.8.31.43.PM.mov

ios Safari -

Screen.Recording.2024-06-07.at.8.56.29.PM.mov

Mweb Safari -

WhatsApp.Video.2024-06-07.at.9.08.52.PM.mp4

Desktop -

Screen.Recording.2024-06-07.at.9.31.31.PM.mov

@ishpaul777
Copy link
Contributor

ishpaul777 commented Jun 7, 2024

Copy link
Contributor

github-actions bot commented Jun 7, 2024

@ishpaul777
Copy link
Contributor

ishpaul777 commented Jun 7, 2024

  1. [HOLD for payment 2024-06-20] [HOLD for payment 2024-06-18] [$500] IOS - Task - Unable to scroll down task description #41567 - fixed

Desktop Chrome -

Screen.Recording.2024-06-07.at.8.34.41.PM.mov

IOS Native -

Screen.Recording.2024-06-07.at.8.05.17.PM.mov

IOS Safari -

Screen.Recording.2024-06-07.at.8.54.17.PM.mov

MWEB chrome -

VIDEO-2024-06-07-21-15-46.mp4

Desktop -

Screen.Recording.2024-06-07.at.9.31.31.PM.mov

Android -

WhatsApp.Video.2024-06-07.at.9.47.04.PM.mp4

@ishpaul777
Copy link
Contributor

ishpaul777 commented Jun 7, 2024

  1. [HOLD for payment 2024-06-20] [HOLD for payment 2024-06-18] [HOLD for payment 2024-06-06] [HOLD #37374][$1000] Text in some languages gets cut off at the bottom in composer on ios #17767 Paste text from issue desc and check if it's displayed properly - fixed

IOS Native -

Screen.Recording.2024-06-07.at.8.10.39.PM.mov

Chrome Desktop -

Screen.Recording.2024-06-07.at.8.35.49.PM.mov

Mweb safari -

Screen.Recording.2024-06-07.at.8.45.52.PM.mov

Mweb chrome

WhatsApp.Video.2024-06-07.at.9.08.52.PM.mp4

Desktop -

Screen.Recording.2024-06-07.at.9.29.36.PM.mov

Android -

WhatsApp.Video.2024-06-07.at.9.44.32.PM.mp4

@ishpaul777
Copy link
Contributor

ishpaul777 commented Jun 7, 2024

  1. [PAID] [HOLD for payment 2024-06-18] [$500] Unable to undo copy and pasted text #39255 - fixed

Chrome -

Screen.Recording.2024-06-07.at.8.17.08.PM.mov

Desktop -

Screen.Recording.2024-06-07.at.9.28.43.PM.mov

Native device cannot be tested.

@ishpaul777
Copy link
Contributor

ishpaul777 commented Jun 7, 2024

  1. [HOLD for payment 2024-06-20] [HOLD for payment 2024-06-18] Live Markdown treats > space and >nospace equally #41696 Check if markdown is treating >test and > test differently (the second one should be a quote, the first one just plain text) - fixed

Android Native -

WhatsApp.Video.2024-06-07.at.9.42.04.PM.mp4

Desktop Chrome -

Screen.Recording.2024-06-07.at.8.21.21.PM.mov

IOS native -

Screen.Recording.2024-06-07.at.8.39.12.PM.mov

IOS Mweb safari -

Screen.Recording.2024-06-07.at.8.42.50.PM.mov

Mweb Chrome -

WhatsApp.Video.2024-06-07.at.9.08.22.PM.mp4

Desktop -

Screen.Recording.2024-06-07.at.9.26.19.PM.mov

@luacmartins
Copy link
Contributor

Thanks @ishpaul777. It seems like #41597 shouldn't be fixed in this PR, so I removed it from the OP. As for #41137, that's no longer a blocker, so I think we can merge this and continue to work on a solution for #41137

@ishpaul777
Copy link
Contributor

Ohk! I have tested rest issues on mweb, ios native and chrome desktop will completed the rest videos as we speak.

@melvin-bot melvin-bot bot requested a review from blimpich June 7, 2024 16:12
@luacmartins luacmartins merged commit e8f8189 into Expensify:main Jun 7, 2024
23 of 24 checks passed
OSBotify pushed a commit that referenced this pull request Jun 7, 2024
…live-markdown-bump

[CP Staging] Bump `react-native-live-markdown` to 0.1.82

(cherry picked from commit e8f8189)
@OSBotify
Copy link
Contributor

OSBotify commented Jun 7, 2024

✋ 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

OSBotify commented Jun 7, 2024

🚀 Cherry-picked to staging by https://github.com/luacmartins in version: 1.4.80-14 🚀

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.

@fabOnReact
Copy link
Contributor

Expensify Composer (When moving to another line, the word and emoji are close to each other):

All tests for Issue #14445 are successfull.

The difference of baseline is 1.15 (barely noticeable), maximumLineHeight 20, maximumFontLineHeight 17.69

Before After
Before After

The result below is achieved after setting textInputCompose.lineHeight: 40.

  • baseLineOffset is 11.15
  • maximumLineHeight is 40
  • maximumFontLineHeight is 17.69
Before After
Before After
Before After

Issue #14445 requires also Meta team to merge PR facebook/react-native#44614.

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 1.4.81-11 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants