[$250] Code blocks of only spaces don't render

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 1.4.1-7
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
**Issue reported by:**Applause - Internal Team
Slack conversation:

Action Performed:

1. Go to any chat
2. Send a text wrapped in two spaced backticks(Eg. Hello ). i.e Have a space between the backticks

Expected Result:

he backtick should be in the code block

Actual Result:

One Backtick is out of the code block

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

Bug6285284_1700561421497.test3_Backtick.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01369e16f895581dbb
• Upwork Job ID: 1726984904265334784
• Last Price Increase: 2024-04-17
• Automatic offers:
• hoangzinh | Reviewer | 0

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01369e16f895581dbb

[melvin-bot]

Triggered auto assignment to @twisterdotcom (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @hoangzinh (External)

[s-alves10]

Proposal

Please re-state the problem that we are trying to solve in this issue.

One backtick is outside the code block when we send hello

What is the root cause of that problem?

Here is the regex for the inline code block

        regex: /(\B|_|)&#x60;(.*?\S.*?)&#x60;(\B|_|)(?!&#x60;|[^<]*<\/pre>)/g,

As you can see, we add negative lookahead assertion ?!` to take the last backtick but didn't take care of the space characters before it.

This is the root cause

What changes do you think we should make in order to solve the problem?

We need to consider the cases where spaces exist before the backtick
Update the above regex to

        regex: /(\B|_|)&#x60;(.*?\S.*?)&#x60;(\B|_|)(?!(\s*&#x60;)|[^<]*<\/pre>)/g,

This works as expected

Result

31633.mp4

What alternative solutions did you explore? (Optional)

In cases we want to parse spaces as a valid code like github, we can update the above regex to

         regex: /(\B|_|)&#x60;(.*?[\S ].*?)&#x60;(\B|_|)(?!&#x60;|[^<]*<\/pre>)/g,

31633_alternative.mp4

[twisterdotcom]

Surely this is a regression from somewhere right? cc @parasharrajat or @allroundexperts might know. I feel like we test markdown endlessly.

[hoangzinh]

@s-alves10 are you able to find any regression PR recently causing this bug? or it's a new case that we haven't handled before?

[s-alves10]

Inline code regex was changed 3 months ago but that change didn't cause this issue.
I don't think this is a recent regression

[parasharrajat]

@twisterdotcom I don't see any recent PR that caused this. but I agree with you that we test MD endlessly. In the past, I raised the same concern and suggested that we should create a ruleset for all MD syntax. I guess we are still on that step. We should create one to make sure we are not redoing it. Let me know your thoughts.

[hoangzinh]

@s-alves10 I tried to apply your proposal but it causes a unit test in expensify-common repo failure. Could you check again? Thanks

[s-alves10]

@hoangzinh

` ` hello ` `
``` ```

Comparing the above two cases, the first case needs to extend the inline code block content as possible including the space character, and the second case needs to extend the content as possible not including the space.

We need to set clear expectation here

Note: I've found that there are some differences in inline code block parsing between GitHub and Expensify. I'd like to know what the Expensify rule is based on

[melvin-bot]

@twisterdotcom, @hoangzinh Whoops! This issue is 2 days overdue. Let's get this updated quick!

[hoangzinh]

We need to set clear expectation here

Agreed. @twisterdotcom @lanitochka17, the expectation is not clearly enough. Could we describe it more clearly? Thanks.

Given user type

` ` hello ` `

What is our expectation in compose box?

1. hello (2 code blocks on 2 sides of hello text, same as Github)
2. or `hello` (backtick on 2 sides of hello text)

[hoangzinh]

I've found that there are some differences in inline code block parsing between GitHub and Expensify. I'd like to know what the Expensify rule is based on

@s-alves10 I don't know too. You can ask in Slack to get the answer.

[parasharrajat]

@hoangzinh Let's think about this problem #31633 (comment) before jumping on proposals.

[hoangzinh]

Oh, I thought we already have unit tests for MD to ensure it won't happen again.

In the past, I raised the same concern and suggested that we should create a ruleset for all MD syntax

@rushatgabhane I wasn't involved before. Could you share more about this point? Thanks

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[twisterdotcom]

FWIW, I think it should render like GitHub: hello .

We are also doing a lot of ExpensiMark updates here: #27977 (comment). Perhaps we should hold Markdown issues on that larger project @parasharrajat / @tomekzaw / @thienlnam?

[tomekzaw]

I believe this issue is related to #31493 but all the other issues in #27977 (comment) seem to be independent.

[thienlnam]

We are also doing a lot of ExpensiMark updates here: #27977 (comment). Perhaps we should hold Markdown issues on that larger project @parasharrajat / @tomekzaw / @thienlnam?

I think we should keep track of all these markdown changes to make sure the expected outcome is correct. Not sure how many of these there are though.

Though since this looks related to #31493, let's just hold this issue on that

[twisterdotcom]

Still waiting on markdown hitting web.

[twisterdotcom]

Waiting on #36071 (comment)

[twisterdotcom]

Still going to wait on live markdown being everywhere.

[twisterdotcom]

This is still a weird little thing:

[melvin-bot]

Upwork job price has been updated to $250

[hoangzinh]

Hi @twisterdotcom is this issue still external or would be picked by @tomekzaw?

[tomekzaw]

@hoangzinh It looks like the root cause of this issue is located in ExpensiMark.

Let's ask @robertKozik from our Live Markdown team at SWM if he wants to come up with a fix or rather make it external.

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[twisterdotcom]

@robertKozik can we assign you or somebody from the Live Markdown team here?

[robertKozik]

Sorry, looking into it right now 👀

[BartoszGrajdek]

Hi! I'm Bartosz from SWM react-native-live-markdown team, I'll be handling this issue together with #39518 you can assign me here 😄

[melvin-bot]

📣 @hoangzinh 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job

[BartoszGrajdek]

@thienlnam this issue was due to expensify-common version inconsistency between live markdown & expensify. Can we get it closed since it's now working the same way both in composer & chat?