Skip to content

feat: adjust lazy-continuation for block quotes and parse > correctly - #231

Merged
Ilia Permiashkin (p3rmiashkin) merged 1 commit into
masterfrom
ilia.permiashkin/md-quotes
Sep 29, 2026
Merged

Ilia Permiashkin (p3rmiashkin) merged 1 commit into
masterfrom
ilia.permiashkin/md-quotes

Conversation

@p3rmiashkin

Copy link
Copy Markdown
Contributor

No description provided.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-29T09:04:56.114541Z 9703f25 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@donnerpeter

Copy link
Copy Markdown
Member

That's a lot of passing lazyBlockQuoteContinuation around in all flavors. Can this be done in some more efficient way? E.g. always disallowing the lazy continuation and some postprocessing in a single place to glue it back together? Or pass as a field in some object that's already propagated everywhere?

@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: 9703f251a3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

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

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

Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".

Comment on lines +77 to +79
// A paragraph lexes the markers in its text itself
if (markersStack.lastOrNull() is ParagraphMarkerBlock) {
return

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Handle paragraph quote markers after list indentation

When a block quote paragraph is nested at least four columns into a list, this early return assumes the inline lexer will recognize a continuation marker that it cannot see as such. For example, - > foo\n > bar produces a Markdown:> token for the second marker and renders literal > bar, because the inline lexer sees four leading spaces while the block constraints know those spaces belong to the list. Paragraph continuation markers need to be emitted or otherwise communicated using the parsed constraints rather than relying solely on inline lexing.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This is a pre-existing bug that can be fixed in a separate MR

@p3rmiashkin
Ilia Permiashkin (p3rmiashkin) merged commit f0b39a3 into master Sep 29, 2026
6 checks passed
@p3rmiashkin
Ilia Permiashkin (p3rmiashkin) deleted the ilia.permiashkin/md-quotes branch September 29, 2026 12:35
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.

2 participants