Chat - Additional lines are shown when editing a text with markdown type Quote

[kavimuru]

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

---

Action Performed:

1. Go to https://staging.new.expensify.com
2. Log in with any account
3. Start conversation
4. Create a text type note for example the following text >This is a test of a note
5. Click on Edit comment

Expected Result:

When editing, the same number of lines as the text of the note must be shown

Actual Result:

An additional blank line above and below the typed text is displayed

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Web
• iOS
• Android
• Desktop App
• Mobile Web

Version Number:
1.0.88-2
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Expensify/Expensify Issue URL:

View all open jobs on GitHub

Issue not repro in production, adding the deploy blocker.

[OSBotify]

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

[MelvinBot]

Triggered auto assignment to @yuwenmemon (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[parasharrajat]

We should remove the newline that is being prepended here in replacement & also from the regex \n?

 {
               name: 'quote',
               regex: /\n?<(blockquote|q)(?:"[^"]*"|'[^']*'|[^'">])*>([\s\S]*?)<\/\1>(?![^<]*(<\/pre>|<\/code>))/gi,
               replacement: (match, g1, g2) => {
                   const resultString = g2.trim().split('\n').map(m => `> ${m}`).join('\n');
                   return `\n${resultString}\n`;
               }
           },

[roryabraham]

AFAICT this has no notable effect on the resulting markdown and isn't creating a real problem. Closing this out.