feat: correctly parse more malformed syntaxes #1316
+748
−4
Conversation
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
we need this because in some cases there is a link node (or smth like an inline code) within the ** markers. and this causes remark-parse to "split" the AST so we have to expand the search into nearby nodes
maximilianfalco
requested review from
eaglethrost,
kevinports and
rafegoldberg
eaglethrost
reviewed
Feb 2, 2026
eaglethrost
reviewed
Feb 2, 2026
eaglethrost
reviewed
Feb 2, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🧰 Changes
This PR is an extension of #1279 and does some things, which involves:
contentParser.fail_back_, we want to italicize the "back")🧬 QA & Testing
Look into the attached tickets and simply copy and paste the page contents, the bold and italics should now be exactly as what the editor shows and is the intended behaviour