Skip to content

[Payment due @ChavdaSachin] Strip incomplete markdown from Concierge streaming drafts#89744

Merged
inimaga merged 8 commits into
mainfrom
claude-stripIncompleteMarkdownDuringStreaming
May 19, 2026
Merged

[Payment due @ChavdaSachin] Strip incomplete markdown from Concierge streaming drafts#89744
inimaga merged 8 commits into
mainfrom
claude-stripIncompleteMarkdownDuringStreaming

Conversation

@MelvinBot

@MelvinBot MelvinBot commented May 6, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

During Concierge streaming, bodyMarkdown arrives via Pusher before the server-rendered finalRenderedHTML is available. Some streamed markdown is incomplete at chunk boundaries (for example, **bold without the closing **, or [text](url without the closing )) and complete emphasis can also briefly leak raw delimiters when a streaming snapshot still contains Markdown-style text such as *Workspaces*.

This PR adds a stripIncompleteMarkdown() sanitization step in buildConciergeDraftReportAction before getParsedComment(). It removes trailing incomplete markdown constructs: unclosed links/images, bold (**), strikethrough (~~), code blocks (```), and inline code (`), so half-finished syntax is hidden until a later streaming chunk completes it.

For completed streamed emphasis, it normalizes **bold** and ~~strike~~ outside code ranges to ExpensiMark single-delimiter syntax (*bold* and ~strike~) before parsing. It also parses Markdown emphasis that arrives through streaming finalRenderedHTML snapshots, including plain text or HTML fragments with text nodes like *Workspaces*. This keeps the word styled during streaming while preventing raw *, **, or ~~ delimiters from flashing in the UI.

The final saved message is unaffected since it uses server-side HTML rendering via finalRenderedHTML.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/633323

Tests

npm test -- --runTestsByPath tests/unit/pages/inbox/conciergeDraftState.test.ts --runInBand --no-watchman

Offline tests

N/A — this change only affects the client-side rendering of streaming Concierge draft messages, which require an active connection.

QA Steps

  1. Login with an Expensifail account
  2. Start a 1-on-1 DM with Concierge
  3. Send it a message, ex: "How do I export a report?"
  4. Observe that the streamed answer doesn't display incomplete markdown format

Current result in Staging

  • Partial markdown is displayed during streaming

Expected result

  • Partial markdown is NOT displayed during streaming

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
  • 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 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 used JaimeGPT to get English > Spanish translation. I then posted it 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.ts 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 new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • 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.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • 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

Resolved.md.rendering.during.streaming.mp4

During Concierge streaming, partial markdown (e.g. unclosed bold,
links, code blocks) was being rendered as raw syntax by ExpensiMark.
Add stripIncompleteMarkdown() to sanitize the tail of bodyMarkdown
before parsing, removing unclosed constructs so they don't flash
briefly in the UI.

Co-authored-by: Issa Nimaga <inimaga@users.noreply.github.com>
@MelvinBot MelvinBot requested a review from a team May 6, 2026 11:24
@inimaga inimaga marked this pull request as ready for review May 6, 2026 11:44
@inimaga inimaga requested a review from a team as a code owner May 6, 2026 11:44
@melvin-bot melvin-bot Bot requested review from ChavdaSachin and trjExpensify and removed request for a team May 6, 2026 11:44
@melvin-bot

melvin-bot Bot commented May 6, 2026

Copy link
Copy Markdown

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

@melvin-bot melvin-bot Bot requested review from a team and dukenv0307 and removed request for a team May 6, 2026 11:44
@melvin-bot

melvin-bot Bot commented May 6, 2026

Copy link
Copy Markdown

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

@github-actions

github-actions Bot commented May 6, 2026

Copy link
Copy Markdown
Contributor

🚧 @inimaga has triggered a test Expensify/App build. You can view the workflow run here.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a283fbbdef

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/pages/inbox/conciergeDraftState.ts Outdated
Comment thread src/pages/inbox/conciergeDraftState.ts Outdated
@MelvinBot

Copy link
Copy Markdown
Contributor Author

The failing checks are not related to this PR's code changes:

  • checklist — PR Author Checklist not yet completed (expected for draft PRs)
  • review — The CI job was canceled (The operation was canceled), not a code failure. This is a transient CI infrastructure issue.

All substantive checks pass: ESLint, typecheck, all 8 test jobs, prettier, spellcheck, React Compiler, storybook, perf-tests, and builds.

Recommendation: Re-run the review check. No code fix is needed.

@github-actions

This comment has been minimized.

@ChavdaSachin

Copy link
Copy Markdown
Contributor

@dukenv0307, does this need my review?

@inimaga

inimaga commented May 6, 2026

Copy link
Copy Markdown
Contributor

@ChavdaSachin Hold off on reviewing this for now.

@inimaga inimaga removed the request for review from dukenv0307 May 6, 2026 11:56
@inimaga inimaga changed the title Strip incomplete markdown from Concierge streaming drafts [Hold] Strip incomplete markdown from Concierge streaming drafts May 6, 2026
@inimaga inimaga requested a review from a team as a code owner May 6, 2026 12:53
@melvin-bot melvin-bot Bot requested review from cretadn22 and removed request for a team May 6, 2026 12:53
@melvin-bot

melvin-bot Bot commented May 6, 2026

Copy link
Copy Markdown

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

@inimaga inimaga removed the request for review from cretadn22 May 6, 2026 12:53
@codecov

codecov Bot commented May 6, 2026

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/pages/inbox/conciergeDraftState.ts 94.95% <97.82%> (+9.24%) ⬆️
... and 123 files with indirect coverage changes

@ChavdaSachin

Copy link
Copy Markdown
Contributor

@inimaga any update here?

# Conflicts:
#	src/pages/inbox/conciergeDraftState.ts
@inimaga

inimaga commented May 18, 2026

Copy link
Copy Markdown
Contributor

@ChavdaSachin This is ready to go. Could you please re-review. If you're to re-perform testing, you need to do so using a test account with the expensifail.com domain, or alternatively private message me an email to be added to the beta.

@github-actions

Copy link
Copy Markdown
Contributor

🚧 @inimaga has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions

Copy link
Copy Markdown
Contributor

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #89744.

Android 🤖 iOS 🍎
⏩ SKIPPED ⏩ ⏩ SKIPPED ⏩
The build for Android was skipped The build for iOS was skipped
Web 🕸️
https://89744.pr-testing.expensify.com
Web

👀 View the workflow run that generated this build 👀

@inimaga inimaga requested a review from ChavdaSachin May 18, 2026 17:30

@ChavdaSachin ChavdaSachin left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! ✅

@ChavdaSachin

Copy link
Copy Markdown
Contributor
Web
Screen.Recording.2026-05-19.at.4.31.49.PM.mov

</details?

Comment thread src/pages/inbox/conciergeDraftState.ts Outdated
@inimaga inimaga requested a review from a team May 19, 2026 12:02
@melvin-bot melvin-bot Bot requested review from ahmedGaber93 and removed request for a team May 19, 2026 12:02
@melvin-bot

melvin-bot Bot commented May 19, 2026

Copy link
Copy Markdown

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

@inimaga inimaga removed the request for review from ahmedGaber93 May 19, 2026 12:03
Co-authored-by: Issa Nimaga <inimaga@users.noreply.github.com>

@ChavdaSachin ChavdaSachin left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

break;
}

codeRanges = getCodeRanges(result).ranges;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ CONSISTENCY-3 (docs)

The strip-then-normalize sequence for bold (lines 172-175) and strikethrough (lines 177-180) is identical apart from the delimiter and its single-character replacement. This 4-line block is duplicated verbatim.

Extract a helper that performs both steps for a given delimiter:

function stripAndNormalizeDelimiter(text: string, delimiter: string, replacement: string, codeRanges: TextRange[]): {result: string; codeRanges: TextRange[]} {
    let updatedRanges = getCodeRanges(text).ranges;
    const stripped = stripUnpairedLastLineDelimiter(text, delimiter, updatedRanges);
    updatedRanges = getCodeRanges(stripped).ranges;
    const normalized = normalizeDelimiterForExpensiMark(stripped, delimiter, replacement, updatedRanges);
    return {result: normalized, codeRanges: getCodeRanges(normalized).ranges};
}

Then the two blocks collapse to:

({result, codeRanges} = stripAndNormalizeDelimiter(result, BOLD_DELIMITER, '*', codeRanges));
({result, codeRanges} = stripAndNormalizeDelimiter(result, STRIKETHROUGH_DELIMITER, '~', codeRanges));

Reviewed at: 583714b | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

@inimaga inimaga merged commit 40223f2 into main May 19, 2026
46 checks passed
@inimaga inimaga deleted the claude-stripIncompleteMarkdownDuringStreaming branch May 19, 2026 12:24
@github-actions

Copy link
Copy Markdown
Contributor

🚧 @inimaga has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

Copy link
Copy Markdown
Contributor

✋ 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
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/inimaga in version: 9.3.78-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

@MelvinBot

Copy link
Copy Markdown
Contributor Author

No help site changes required.

This PR adds a stripIncompleteMarkdown() sanitization step to hide raw markdown syntax (unclosed bold, links, code blocks, etc.) that briefly flashes during Concierge message streaming. It's a purely technical rendering fix — no user-facing features, settings, labels, or workflows are added or changed, so no updates to App/docs/articles are needed.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/roryabraham in version: 9.3.78-1 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@melvin-bot

melvin-bot Bot commented May 21, 2026

Copy link
Copy Markdown

🤖 Payment issue created: #91351

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants