[JEWEL-1256] Fix incremental Markdown parsing for table rows#3428
Closed
AlexVanGogen wants to merge 1 commit into
Closed
[JEWEL-1256] Fix incremental Markdown parsing for table rows#3428AlexVanGogen wants to merge 1 commit into
AlexVanGogen wants to merge 1 commit into
Conversation
DanielSouzaBertoldi
approved these changes
Mar 10, 2026
daaria-s
approved these changes
Mar 18, 2026
Collaborator
|
@AlexVanGogen solve conflicts then we can merge :) |
AlexVanGogen
force-pushed
the
alexvangogen/JEWEL-1256-new-table-rows
branch
from
91038b8 to
ac62b0a
Compare
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
AlexVanGogen
force-pushed
the
alexvangogen/JEWEL-1256-new-table-rows
branch
from
ac62b0a to
4d86eb4
Compare
AlexVanGogen
force-pushed
the
alexvangogen/JEWEL-1256-new-table-rows
branch
from
4d86eb4 to
48c6b7f
Compare
…ter table header When typing in the Markdown editor, a line starting with `|` immediately after a table header was initially parsed as a paragraph. As the user continued typing (e.g., `| A | B |`), the line should become a table row, but incremental parsing didn't re-evaluate the preceding table block, causing the row to remain a separate paragraph. This change introduces `allowsMergingWithNextBlock` property to `MarkdownBlockProcessorExtension`, allowing extensions to indicate that they can absorb subsequent blocks during re-parsing. The `MarkdownProcessor` now checks this property and includes the preceding block in the re-parse range when appropriate.
AlexVanGogen
force-pushed
the
alexvangogen/JEWEL-1256-new-table-rows
branch
from
48c6b7f to
2fd51ca
Compare
Collaborator
|
Ready to merge |
intellij-monorepo-bot
pushed a commit
that referenced
this pull request
May 11, 2026
…ter table header When typing in the Markdown editor, a line starting with `|` immediately after a table header was initially parsed as a paragraph. As the user continued typing (e.g., `| A | B |`), the line should become a table row, but incremental parsing didn't re-evaluate the preceding table block, causing the row to remain a separate paragraph. This change introduces `allowsMergingWithNextBlock` property to `MarkdownBlockProcessorExtension`, allowing extensions to indicate that they can absorb subsequent blocks during re-parsing. The `MarkdownProcessor` now checks this property and includes the preceding block in the re-parse range when appropriate. closes #3428 GitOrigin-RevId: 7601f504870a216af4e0eb7e7cb031b48d7302ab
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
4 participants
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.
Description
When typing in the Markdown editor, a line starting with
|immediately after a table header was initially parsed as a paragraph. As the user continued typing (e.g.,| A | B |), the line should become a table row, but incremental parsing didn't re-evaluate the preceding table block, causing the row to remain a separate paragraph.This change introduces
allowsMergingWithNextBlockproperty toMarkdownBlockProcessorExtension, allowing extensions to indicate that they can absorb subsequent blocks during re-parsing. TheMarkdownProcessornow checks this property and includes the preceding block in the re-parse range when appropriate.Examples
Before
Screen.Recording.2026-02-13.at.13.28.03.mov
After
Screen.Recording.2026-02-18.at.15.38.20.mov
Release notes
Bug fixes
Note
Medium Risk
Changes incremental parsing boundaries in
MarkdownProcessorand extends the experimentalMarkdownBlockProcessorExtensionAPI, which could affect editor-preview parsing behavior for other custom blocks if misconfigured.Overview
Fixes editor-mode incremental Markdown parsing so blocks like GFM tables can absorb a following paragraph when edits turn it into a table row.
This introduces
MarkdownBlockProcessorExtension.allowsMergingWithNextBlock(defaultfalse) and updatesMarkdownProcessorto include the preceding custom block in the reparse range when that flag is enabled.Enables the flag for the GFM tables processor and adds a dedicated
gfmTables.testsmodule plus JUnit tests covering the table-header-to-row incremental typing scenarios.Written by Cursor Bugbot for commit 4d86eb4. This will update automatically on new commits. Configure here.