[HOLD for payment 2024-06-21] [$250] mWeb - Chat - Quote markdown is not applied

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 1.4.82-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to https://staging.new.expensify.com/home
2. Tap on report
3. Enter >hsjd
4. Send the message

Expected Result:

Quote markdown must be applied

Actual Result:

Quote markdown is not applied

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6503955_1717682774519.Screenrecorder-2024-06-06-19-33-11-542.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0162a44a8fd308afd5
• Upwork Job ID: 1798839739922152623
• Last Price Increase: 2024-06-06
• Automatic offers:
• ishpaul777 | Contributor | 102639567

Issue Owner

Current Issue Owner: @anmurali

[melvin-bot]

Triggered auto assignment to @bondydaa (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[lanitochka17]

@bondydaa FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[lanitochka17]

We think that this bug might be related to #vip-vsp

[dragnoir]

Not a deploy blocker.

Offended PR Expensify/expensify-common#691

this is a new expected behavior:

This PR changes quote regex to enforce following space after >.
not followed by space won't be parsed as quote. In the multiple level quote context spaces between > signs are irrelevent

[roryabraham]

If this is indeed the new expected behavior, then react-native-live-markdown needs to be updated such that it's using the new rule. Because right now it's confusing that the markdown processing in the composer is different than what we show in the chat. I think this is a legitimate blocker.

[roryabraham]

These are our options:

• ignore this inconsistency, let this 🐛 go to prod for the time being.
• revert [TS migration] Update expensify-common usage in NewDot #42387
• push forward Bump expensify-common to 2.0.10 react-native-live-markdown#360
• Include Recognise only blockquotes followed by space expensify-common#691 in react-native-live-markdown via a patch

in any event, both PRs need to be included in the same release, or we'll have this inconsistency