docs: update client-side markdown processing for Svelte frontend - #75
Merged
WilliamAGH merged 1 commit intoJul 17, 2026
Conversation
detail-appBotforce-pushed
the
detail/fix-docs/docs-update-client-side-markdown-processing-for-sv-107ab3
branch
from
July 16, 2026 21:59
364c1c4 to
747a7e4CompareUh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The client-side processing documentation referenced deleted files
(chat.html, guided.html, markdown-utils.js) and described a server-first
fallback pattern that no longer exists. Updated to reflect the current
Svelte frontend architecture using parseMarkdown() with streaming-aware
parsing, Java language detection, and DOMPurify sanitization.
Also added missing JSDoc for the isStreaming parameter in parseMarkdown(),
which is critical for proper streaming-aware markdown handling.
Example: Without this fix, a developer following the docs would look for
markdown-utils.js which no longer exists, or assume server round-trips
during streaming when the client handles markdown locally.
Introduced by commit e35ef82 (@WilliamAGH)
Doc Drift PRs can be configured here.