fix(editor): stabilize visual markdown escaping#548
Merged
Conversation
Preserve live inline code source using the configured serializer while keeping HTML- and escaped-link-looking visual input literal. Closes #542
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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 free
to 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.
Summary
\[for escaped link-looking literals because Markra reserves it as a math delimiterWhy
Issue #542 exposed multiple cases where visual input intent and serialized Markdown diverged. Simple live Markdown should retain its source, while source-level HTML and backslash-escaped link syntax typed in the visual editor should remain literal text across save and reload.
Validation
pnpm testpassed: 2,409 testspnpm buildpassedRisk
Related Issues