[Due for payment 2025-03-25] Reports - Description with mark down is rendered as HTML tag

[mitarachim]

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: 9.1.11-4
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): applausetester+110301kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Search

Action Performed:

1. Go to staging.new.expensify.com
2. Log in with a new account.
3. Submit an expense to a user, with text containing mark down as description. Do not enter merchant.
4. Go to Reports.

Expected Result:

Description field will not show the mark down as HTML tag.

Actual Result:

Description field shows the mark down as HTML tag.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6768397_1741770460004.20250312_170331.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @sakluger

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @sakluger (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

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

[daledah]

🚨 Edited by proposal-police: This proposal was edited at 2025-03-12 09:47:25 UTC.

Proposal

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

Description field shows the mark down as HTML tag.

What is the root cause of that problem?

It seems that BE is returning description in a different format which makes the parse function we are using here wrong.

App/src/components/SelectionList/Search/TransactionListItemRow.tsx

Lines 150 to 153 in 9b51ab8

	if (!merchantOrDescriptionToDisplay && !isLargeScreenWidth) {
	merchantOrDescriptionToDisplay = Parser.htmlToText(Parser.replace(description));
	}
	let merchant = transactionItem.shouldShowMerchant ? merchantOrDescriptionToDisplay : Parser.htmlToText(Parser.replace(description));

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

We should remove Parser.replace(description) only use Parser.htmlToText(description)

    if (!merchantOrDescriptionToDisplay && !isLargeScreenWidth) {
        merchantOrDescriptionToDisplay = Parser.htmlToText(description);
    }
    let merchant = transactionItem.shouldShowMerchant ? merchantOrDescriptionToDisplay : Parser.htmlToText(description);

OR we can use Parser.htmlToMarkdown if we want to show markdown

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

None

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.